New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 769196 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug

Blocking:
issue 771005



Sign in to add a comment

Focus does not shift to 'Advanced' section of chrome://settings/clearBrowserData page.

Reported by db...@etouch.net, Sep 27 2017

Issue description

Chrome Version: 63.0.3225.0 Revision 454b29bb89471156174c8769692ec607f8209f94-refs/heads/master@{#504540} 
OS: Windows (7,8,8.1,10),Mac OS X(10.12.6)

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://settings/clearBrowserData page
(2) Press Tab key or right/Left arrow observe focus

Actual: Focus does not shift to Advanced section after pressing Tab key or right/Left arrow .

Expected: Focus should shift to Advanced section.

This is a Non-regression issue, seen from M-63(63.0.3225.0)

 
Actual_Focus.mov
2.6 MB Download

Comment 1 by db...@etouch.net, Sep 27 2017

Description: Show this description
Status: Untriaged (was: Unconfirmed)
Changing the status to Untriaged, so that the issue would get addressed.
Thank You.

Comment 3 by dpa...@chromium.org, Sep 27 2017

Labels: Proj-MaterialDesign-WebUI
Owner: dullweber@chromium.org
Status: Assigned (was: Untriaged)
Thanks for reporting this, I tried it and I'm able to reproduce the following:

1. press tab - the close button 'X' gets focused
2. press tab - the "basic" tab gets focused, indicated by changing it to a bold font
3. press right arrow - the "advanced" tab is focused
4. press enter - the view is switched to the advanced tab
5. press tab again and the first item on the currently selected tab is focused.

I assume you expect that step 4 shouldn't be required?

chrome://settings/certificates behaves in the same way. (afaik this site only exists on linux)
Other webui interfaces that are using paper-tabs also behave this way.

The cookie view that can be opened from the page info bubble doesn't require the user to press enter. 

It looks like this is an inconsistency between web ui and native ui in Chrome. I'm not sure which approach is preferred but I will ask in the accessibility review.
Blocking: 771005
Status: Fixed (was: Assigned)
The native ui and web ui are not consistent but as it is still possible to completely operate the dialog by keyboard, I will close this bug.
Status: WontFix (was: Fixed)

Sign in to add a comment