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

Issue 793249 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 903557
Owner:
Closed: Nov 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Chromevox focus is not seen completely on ubertray in OOBE screen.

Project Member Reported by kebalaji@chromium.org, Dec 8 2017

Issue description

Chrome Version: 64.0.3282.14/10176.7.0 dev channel Kip,Reks,Daisy
OS:Chrome OS

What steps will reproduce the problem?
(1)Recover build>> In OOBE screen, Click on Accessibility
(2)Enable Chromevox, Mute the volume and enable On-screen keyboard
(3)Keep tabbing until the focus reaches Ubertray and observe

Expected:Chromevox Focus should be seen on entire ubertray
Actual: Instead, Focus is not seen completely on ubertray

This is a Regression issue as same is working fine in 64.0.3271.0/10139.0 dev

NOTE: Issue is not seen on Linux and Windows

@dmazzoni: Please confirm the issue
 
ActualUbertrayCF.mp4
5.4 MB View Download
ExpectedUbertrayCF.mp4
4.7 MB View Download
Owner: abodenha@chromium.org
Even with ChromeVox off, the focus rings for the ubertray look wrong. To @abodenha to delegate.

Cc: r...@chromium.org alemate@chromium.org
Components: -UI>Accessibility -UI>Shell>StatusArea UI>Shell>OOBE
Labels: -ReleaseBlock-Stable
Owner: ----
Status: Untriaged (was: Assigned)
Owner: r...@chromium.org
rkc@ can you assign this?

Comment 4 by r...@chromium.org, Mar 3 2018

Owner: alemate@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by r...@chromium.org, Mar 3 2018

Owner: wzang@chromium.org
Actually, Colin, this may be related to your code for the shelf.

Comment 6 by wzang@chromium.org, Mar 3 2018

Cc: est...@chromium.org
Per #1 this issue is not specific to Chromevox, so this looks identical to  issue 730964 .

+estade@

Comment 7 by wzang@chromium.org, Mar 3 2018

Will verify if this issue is still reproducible after  issue 730964  is fixed.
Mergedinto: 903557
Status: Duplicate (was: Assigned)

Sign in to add a comment