Issue metadata
Sign in to add a comment
|
a11y: alt + f or alt + e should open menu regardless of which key is released first |
||||||||||||||||||||||||||
Issue descriptionGoogle Chrome 66.0.3353.0 (Official Build) canary (64-bit) (cohort: Clang-64) Steps to repro: # Launch Chrome on any page except Google Docs (or an app that takes keystrokes) # Press and release Alt Expected/actual: focus lands on the Customize and Control menu (upper right corner). This was made due to a user request a long time ago. # Press alt + f, holding down alt the entire time (press and hold alt, press and hold f, let go of f, let go of alt.) This behavior is covered in related bug 817008 # Press alt + f, releasing the alt key before releasing f (press and hold alt, press and hold f, let go of alt, let go of f) Actual: Chrome menu opens Expected from nektar@: "Chrome shouldn't go to the Chrome menu bar if Alt is pressed with another key and Alt is released before that other key is released."
,
Feb 27 2018
Marking bug 817008 as a blocked on bug. This is because if we decide to eliminate the alt + f opening the Chrome menu entirely, this bug becomes a moot point. If this bug is to be fixed in parallel or before 817008, please feel free to remove it from the blocked on field.
,
Feb 27 2018
After discussions with dmazzoni@, this should be closed as WontFix. We don't want this behavior, we don't want the order of key release to matter. As for the root of opening this bug, there was confusion as to whether or not the key order was having an effect on the menu opening. I can't reproduce that: doing both versions of alt + f described above are the same, I can't reproduce the release ordering making a difference.
,
Feb 28 2018
Reopening after reports of screen readers causing this bug
,
Feb 28 2018
Google Chrome 66.0.3356.0 (Official Build) canary (64-bit) (cohort: Clang-64) Without a screen reader: the ordering of when you release Alt and f as described above doesn't matter, either way it will open the Chrome menu. With JAWS 2018.1802.78 64-bit English: hold down alt, then press f. Menu opens. Release the alt key before the f key: the find menu opens and starts filling with f characters. With NVDA 2017.4: hold down alt, then press f. Menu opens. Release the alt key before the f key: the find menu opens and starts filling with f characters.
,
Feb 28 2018
CCing nektar@ since he's seeing different behavior from me
,
Mar 1 2018
Since this turns out to be a timing related bug specific to Chrome + Docs + JAWS, I'm going to close this bug out as a dupe of this new bug:817662 Otherwise, this would just get to be too confusing since that bug has a ton of information. |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Feb 27 2018