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

Issue 843964 link

Starred by 2 users
Status: WontFix
Owner:
sammiequon@chromium.org
Closed: May 2018
Cc:
ajha@chromium.org
█ brajkumar@chromium.org
steve...@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Non-Regression : 'Tab' focus is seen missing on 'PIN or password' option in chrome://settings/lockScreen page

Project Member Reported by mmanchala@chromium.org, May 17 2018 
Chrome Version:  68.0.3431.0/10682.0.0 dev-channel Daisy,Candy and Reks
OS: Chrome

What steps will reproduce the problem?
(1)Sign into User -> Go to chrome://settings -> Now under 'People' section click on 'Screen lock' option
(2)Now enter User Password in 'Confirm your password' dialog box -> observe default focus is on 'Password only' option -> press 'Tab' button and observe focus is not seen on 'PIN or password' option
(Please refer Video)

Expected: 'Tab' focus should be  seen on 'PIN or password' option
Actual:  Instead 'Tab' focus is seen missing on 'PIN or password' option

This is Non-Regression Issue as 'Screen lock' is introduced from M-57

@sammiequon: Please confirm the Issue
Actual_NoTabFocusOnPINOption.webm
1.0 MB View Download

Comment 1 by sammiequon@chromium.org, May 17 2018 

I don't think this is a bug. The entire radio group gets focus and the focus indicator is that the current selected item is highlighted. You can then use up and down to navigate through the selections.

This is how it works in the rest of settings (and all of web ui I would think).

Comment 2 by dpa...@chromium.org, May 17 2018

Status: WontFix (was: Assigned)
Hitting tab while the focus is on a radio button, moves the focus to the next element after the radio group. Instead down arrow should be used if the focus is to be moved (along with the selection) to the next radio button. AFAIK, this thas been the case for a while now. You can verify this is also the behavior of the "On startup" section in chrome://settings.
►

Sign in to add a comment