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

Issue 595604 link

Starred by 3 users
Status: Verified
Owner:
dtseng@chromium.org
Closed: Apr 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
pucchakayala@chromium.org
█ brajkumar@chromium.org
kathrelk...@chromium.org
dhadd...@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

[Regression]: Flickering of OOBE screen is seen and unable to go further on enabling Chromevox options

Project Member Reported by sc00335...@techmahindra.com, Mar 17 2016 
Version: 51.0.2679.0/8074.0.0 (Official Build) dev-channel peppy,quawks,gnawty,daisy
OS: Chrome os

What steps will reproduce the problem?
(1) Recover 51.0.2679.0/8074.0.0 via USB
(2) In OOBE screen enable Chromevox option from accessibility section and observe

Expected: Should be able to navigate to EULA screen from OOBE screen even after enabling Chromevox

Actual: Instead black screen flashes continuously and unable to navigate to EULA screen.

This is a regression issue as it is working fine in 49.0.2623.95/7834.60.0 beta channel daisy

NOTE: Without enabling Chromevox from OOBE screen able to navigate to EULA Screen and work

Comment 1 by ajha@chromium.org, Mar 17 2016

Cc: dhadd...@chromium.org pucchakayala@chromium.org
Components: UI>Shell>OOBE
Status: Untriaged (was: Unconfirmed)
Able to reproduce this on 51.0.2679.0/8074.0.0 (Official Build) dev-channel  daisy.

Comment 2 by dhadd...@chromium.org, Mar 17 2016

Cc: kathrelk...@chromium.org

Comment 3 by pbath...@chromium.org, Mar 17 2016 

Issue is not reproducible on 50.0.2661.37/7978.20.0 dev-channel daisy

Comment 4 by lpalmaro@chromium.org, Mar 28 2016

Owner: dtseng@chromium.org
Status: Assigned (was: Untriaged)
[Triage] Assigning to David for further investigation

Comment 5 by pbath...@chromium.org, Apr 6 2016

Status: Verified (was: Assigned)
The fix for https://bugs.chromium.org/p/chromium/issues/detail?id=597000 seems to have fixed this issue too.

Verified on daisy on 51.0.2699.0 / 8155.0.0.
►

Sign in to add a comment