CTRL-W, CTRL-T, ... should be forwarded to X11 apps running in a Crostini container
Reported by
markus@chromium.org,
Apr 23 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10539.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3383.0 Safari/537.36 Platform: 10539.0.0 (Official Build) dev-channel eve Steps to reproduce the problem: 1. Open a terminal window with CTRL-ALT-T 2. vmc start dev 3. run_container.sh --container_name=stretch --user=superman --shell 4. apt-get install -y xterm 5. xterm & 6. try to enter CTRL-W or CTRL-T at the shell prompt. Realize that ChromeOS intercepts these keystrokes and does it's own thing. CTRL-W is particularly devastating. What is the expected behavior? A lot of the "standard" browser shortcuts are commonly used by all sorts of X11 applications. What went wrong? The browser should not try to intercept keys. In particular, closing windows without warning (CTRL-W) is a pretty horrible user experience. Did this work before? N/A Chrome version: 67.0.3383.0 Channel: n/a OS Version: 10539.0.0 Flash Version: I realize that this is still very early days for containers and things are likely going to change a lot. This is just a bug to make sure that the final release won't accidentally forget to address this problem.
,
Sep 28
if you're using crosh in a tab, this is WAI. please see the FAQ: https://chromium.googlesource.com/apps/libapps/+/HEAD/nassh/doc/FAQ.md#How-do-I-send-Ctrl_W_Ctrl_N-or-Ctrl_T-to-the-terminal if you want to use the "correct" workflow, then you shouldn't be using crosh in the first place. you should be running the Terminal app. please see the public docs: https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md#Quickstart nowhere publicly (or really even internally) do we recommend people use crosh and start vms/containers by hand. |
||
►
Sign in to add a comment |
||
Comment 1 by weifangsun@chromium.org
, Sep 28