Focus gets stuck on 'Add printers' button on chrome://devices page
Reported by
vineetha...@etouch.net,
Apr 18 2018
|
||||||||||
Issue descriptionChrome Version: 67.0.3396.10 (Official Build) Revision 5f5009767d16328f4a3c8c4cc6610a7f8bfe0d9e-refs/branch-heads/3396@{#66}(64 bit) OS: Mac(10.12.6, 10.13.1, 10.13.5) What steps will reproduce the problem? (1) Launch chrome, navigate to 'chrome://settings/cloudPrinters'. (2) Click on 'Manage Cloud Printer devices' option to navigate to 'chrome://devices/'. (3) Press tab to traverse the focus throughout the page till the focus reaches the 'Add printers' button for the second time and observe. Actual: Focus gets stuck on 'Add printers' button and unable to click the button with keyboard keys(Enter/Space bar). Expected: Focus should not get stuck on 'Add printers' button and should be able to click the button with keyboard keys(Enter/Space bar). This is a Non-regression issue, seen from M-61 build #61.0.3113.0. NOTE: Issue is also seen on Stable(build #66.0.3359.117) and Canary(build #68.0.3399.0)
,
Apr 27 2018
Is chrome://devices owned by print-preview team?
,
Apr 27 2018
,
May 23 2018
,
May 26 2018
- This does not happen if one navigates to chrome://devices directly. Only when one starts from the settings page and opens chrome://devices from there. - When one closes the settings page, or navigates it elsewhere, then the chrome://devices page that exhibited this problem stops having problems.
,
Jun 14 2018
To varkha@ for triage/routing for Settings, then.
,
Jul 20
Unassigning since I am no longer in Chrome.
,
Jul 20
Assigning to dpapad@ for initial triage.
,
Jul 25
Debugged this for a bit. Observations below: - I am able to reproduce this only on a Mac and only on Chrome builds. Chromium builds work fine (so I was not able to narrow it down with bisect-builds). - It's really strange that once the button is focused a 2nd time, the entire page stops receiving any keyboard events. It's not just that focus is stuck. Pressing "Enter" also does not trigger the button. Could not find something wrong with the page itself, which makes me think that this could be a Blink issue. I also have no explanation on why this is happening only on Mac.
,
Jul 25
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by rbasuvula@chromium.org
, Apr 18 2018