New issue
Advanced search Search tips

Issue 896094 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Meta modifier state is wrong on keydown and keyup events on Linux

Project Member Reported by jamiewa...@chromium.org, Oct 17

Issue description

Chrome Version: 69.0.3497.100, 70.0.3538.67 and 71.0.3573.0 (tested; maybe others)
OS: Linux

What steps will reproduce the problem?
(1) Visit http://w3c.github.io/uievents/tools/key-event-viewer.html
(2) Press and release modifier keys, including Meta (or Win, or Cmd, depending on your keyboard).

What is the expected result?
The appropriate modifier flag is set on the keydown event, and not set on the keyup. Specifically, when pressing either the right or left Meta key, the |meta| flag should be set on the keydown event, but not on the keyup event. This is true for the other modifier keys, and for Meta on Windows and Mac.

What happens instead?
The |meta| flag is set on the keyup event, but not on the keydown event.
 
Cc: rkjnsn@chromium.org
Cc: bokan@chromium.org
Status: Available (was: Untriaged)
I'm guessing this is important for Chromoting in some way? input-dev doesn't have any keyboard expertise anymore nor any spare cycles, if this is urgent - can someone from Chromoting pick it up? If not, can we mark it as P3?
Cc: garykac@chromium.org
Labels: -Pri-2 Pri-3
P3 is fine for me. It causes problems for Chromoting because we use those modifier state flags to detect missing keyup events (for example, if the user locks the workstation with Alt+L, we see a keydown for Alt but no corresponding keyup). Since it's obvious from context in this case that the modifier should be set, it's easy enough to work around it.

Sign in to add a comment