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

Issue 752887 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug-Regression



Sign in to add a comment

Regression : Grey Focus at Uber Tray is not seen properly on clicking Volume Icon

Project Member Reported by mmanchala@chromium.org, Aug 7 2017

Issue description

Chrome Version:  62.0.3176.0/9816.0.0 dev-channel Blaze,Falco and Reks
OS: Chrome

What steps will reproduce the problem?
(1)Recover build  -> In OOBE screen click on Uber Tray 
(2)Now click on Volume Icon i.e. Mute it and again enable Volume -> Observe movement of Grey Focus at Uber Tray (Please refer Video and screenshot)

Expected: On clicking Volume Icon movement of Grey Focus should be seen properly at Uber Tray
Actual: Instead Grey Focus at Uber Tray is not seen properly i.e. observe Focus  on 'US'

This is Regression Issue seen from 61.0.3136.5//9672.0.0
dev-channel Falco

@tbuckley : Please confirm the Issue
 
Actual_ImproperFocus.mp4
12.9 MB View Download
Actual_ImproperFocus.jpg
337 KB View Download
Expected_Focus.mp4
9.8 MB View Download
Any update on this bug? We are going for a stable RC next week and this is marked as a blocker. 
Any update on this one? We are planning to build a R62 stable RC the evening of the 19th, so we would need to have all fixes merged back to 62 in ~24 hours. 
Labels: -Pri-1 Pri-0
Upping priority, as we build our stable RC tomorrow, we need a fix in the next 24 hours.
Cc: abodenha@chromium.org
Cc: tbuck...@chromium.org
Owner: zork@chromium.org
@Zach, is someone on your team able to look at this?

Note that this is a visual bug. The system menu is still entirely functional, and I think it's fairly rare that users will interact with the system menu much during OOBE.

Comment 6 by zork@chromium.org, Oct 23 2017

Cc: zork@chromium.org
Owner: minch@chromium.org
Min, could you look into this?

Comment 7 by minch@chromium.org, Oct 23 2017

Sure, I can do the bisect first.

Comment 8 by minch@chromium.org, Oct 24 2017

Think the release block tag can be removed and issue can be closed. Since it has been fixed in the latest M62 version 62.0.3202.67.
Through bisect, https://chromium.googlesource.com/chromium/src/+/3c86f1b987cbe08d7e9034f29f5b7f853c85126e
fixed the issue.

Comment 9 by minch@chromium.org, Oct 24 2017

Status: WontFix (was: Assigned)

Sign in to add a comment