Issue metadata
Sign in to add a comment
|
[CVox] Issue using search key in canary |
||||||||||||||||||||||||||
Issue descriptionChrome Version: 59.0.3035.0 OS: Chrome When I try to use ChromeVox and the search key with the arrows or with any letters for jump commands, I can't. Every time I press search as part of a keyboard command, the app launcher pops up, and then I can only navigate the app launcher.
,
Mar 10 2017
My recent accelerator changes have just been moving code from one place to another, nothing new. There was that caps lock issue you worked on a month ago, https://codereview.chromium.org/2686833005/ Otherwise nothing comes to mind. +mfomitchev in case he can think of recent app list changes.
,
Mar 10 2017
I can't reproduce this either. Might be best to get the device here rather than hunting it down any other way.
,
Mar 15 2017
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by afakhry@chromium.org
, Mar 10 2017Labels: OS-Chrome
I tried to repro on the same above version, but couldn't. Not sure under which circumstances this would trigger. James, From the bug description, it seems that TOGGLE_APP_LIST is triggering on press. Looks like you have been making some changes in the accelerator* files lately. Are you aware of any recent change that could cause this? Notice, we have two accelerators to trigger TOGGLE_APP_LIST: {true, ui::VKEY_BROWSER_SEARCH, ui::EF_NONE, TOGGLE_APP_LIST}, and {false, ui::VKEY_LWIN, ui::EF_NONE, TOGGLE_APP_LIST}, as you can see one of them is triggered on press and the other is triggered on release. But I don't know if our Search key was recently mapped to VKEY_BROWSER_SEARCH? Any ideas?