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

Issue 777357 link

Starred by 1 user
Status: WontFix
Owner:
█ yoshiki@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
█ krajshree@chromium.org
ajha@chromium.org
█ brajkumar@chromium.org
peter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Focus traversal is not proper in Do not disturb overlay in Notifications

Project Member Reported by kebalaji@chromium.org, Oct 23 2017 
Chrome Version:64.0.3246.0/10059.0.0 dev-channel Daisy,Candy,Reks
OS:Chrome OS

What steps will reproduce the problem?
(1)Sign into user >> Take a screenshot
(2)Click the Notifications icon and click on the settings icon >>Keep tabbing until the focus reaches the settings icon in Do not disturb overlay and again tab >>Observe

Expected: After focus reaches the settings icon in Do not disturb overlay, when tabbed, focus should navigate to Do not disturb toggle button.

Actual: Instead, After tabbing twice, focus is seen on Do not disturb toggle button.

This is a Regression issue as same is working fine in  64.0.3241.0/10038.0.0 dev channel Kip

Note: 1. Issue is not seen in Linux,Windows OS
      2. Considering 64.0.3241.0/10038.0.0 dev channel  as good build because the buttons in the 
         Do not disturb overlay are below and in 64.0.3246.0/10059.0.0 dev-channel, the buttons 
         are above the toggle button.


@yoshiki : Please confirm the issue
ExpectedButtons.jpg
1.8 MB View Download
ActualButton.mp4
2.7 MB View Download

Comment 1 by kebalaji@chromium.org, Oct 23 2017

Summary: Regression: Focus traversal is not proper in Do not disturb overlay in Notifications (was: Regression: )

Comment 2 by yoshiki@chromium.org, Nov 2 2017

Status: WontFix (was: Assigned)
The button bar on the settings panel is redesigned and this issue is gone.

I also found another issue on the current settings panel and filed it.
https://bugs.chromium.org/p/chromium/issues/detail?id=780747
►

Sign in to add a comment