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

Issue 740860 link

Starred by 3 users
Status: Verified
Owner:
afakhry@chromium.org
Closed: Aug 2017
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
ovanieva@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

Regression: ChromeVox (Spoken Feedback) is not correctly reading 'Night Light' button in Ubertray.

Project Member Reported by jbanavatu@chromium.org, Jul 11 2017 
Chrome Version: 61.0.3153.0/9733.0.0 dev channel Falco, Parrot & Paine
OS: Chrome OS

What steps will reproduce the problem?
(1)Sign-in to chrome or Browse as guest >> Open Uber tray >> Enable Chrome Vox (Spoken Feedback) option in Accessibility
(2)Now in Uber tray hit tab  till you reach 'Night Light' button and Observe.

Expected: ChromeVox spoken feedback should read Night Light button as 'Night Light Button Not pressed/ Pressed' 
Actual: Instead, it reads as 'Night Light: dollar 1 Button Not pressed/Pressed.

This is regression issue as it is working fine in 60.0.3112.20/9592.11.0 dev channel Daisy.

Attaching screen shots for reference.
Actual.jpg
4.7 MB View Download
Expected.jpg
3.3 MB View Download

Comment 1 by ketakid@google.com, Aug 31 2017

Cc: ovanieva@chromium.org
Owner: afakhry@chromium.org
afakhry@ what should we do with this stable blocker. ovanieva@ wdyt? Would we block stable for this?

Comment 2 by ovanieva@google.com, Aug 31 2017 

I believe Afakhry@ fixed it. Definitely not a stable blocker - the feature is behind a flag.

Comment 3 by afakhry@chromium.org, Aug 31 2017

Status: Fixed (was: Untriaged)
This has already been fixed. See: https://bugs.chromium.org/p/chromium/issues/detail?id=706067#c16
Project Member

Comment 4 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Aug 31 2017

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-61; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-61 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 13 2017

Labels: -Merge-TBD

Comment 6 by mkarkada@chromium.org, Nov 10 2017

Status: Verified (was: Fixed)
Verified on M64 dev build (10115.0.0, 64.0.3264.0).
►

Sign in to add a comment