Chrome OS: Keyup not sent for 'Search'-key-modified keystrokes if 'Search' key released first |
||||
Issue descriptionChrome Version: 69.0.3497.95 OS: Chrome OS What steps will reproduce the problem? (1) Go to keyboard event viewer: https://cdn.rawgit.com/w3c/uievents/gh-pages/tools/key-event-viewer.html (2) Press and hold the 'Search' key. (3) Press the Right Arrow key. (4) Release the 'Search' key. (5) Release the Right Arrow key. What is the expected result? Keyboard event viewer should report a release event for End. What happens instead? Keyboard event viewer reports a release event for ArrowRight. End never receives a release event. This is important as apps may use keydown/up events as triggers for continued behavior. Note that this will happen with ANY 'Search'-modified key combination on Chrome OS: F-keys, cursor keys, etc. Recommend either: 1. Latching keydown and sending release event for originally intended keypress regardless of 'Search' key status. 2. Sending release event for modified keystroke when 'Search' key is released. 3. Sending release event for both modified and unmodified keys when key is released (that is, track the set of keypresses initiated until release).
,
Nov 1
,
Nov 5
Is this related to keyboard lock or is this the standard ChromeOS behavior? If keyboard lock is not involved, then we should reassign this bug to someone who works on the ChromeOS input pipeline.
,
Nov 5
This does not involve keyboard lock. Could you please help reassign, though, Joe? Not sure who manages this input flow.
,
Nov 21
Sorry for the delay, I'm not 100% sure who to assign this to but I'm thinking that someone involved with CrOS keyboard accelerators would know who to route it to.
,
Nov 21
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ftsui@google.com
, Nov 1Labels: OS-Chrome
Owner: joedow@chromium.org