New issue
Advanced search Search tips

Issue 872266 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Chrome Vox activated on all chrome profiles

Project Member Reported by jasminvu@google.com, Aug 8

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36

Steps to reproduce the problem:
1. Open chrome in two different profiles
2. Have Chrome Vox extension in both profiles, disabled
3. Navigating in both profiles should work as usual
4. Turn on Chrome Vox in one profile. As expected it's turned on and aria labels are being read out.
5. Now use the second profile. I would expect that Chrome Vox is not activated in this profile. However it still reads out all labels. 

What is the expected behavior?
I expect that Chrome Vox is only working in the profile where I activated it.

What went wrong?
Chrome Vox is activated in all open Chrome profiles, instead of in the one where I activated it.

Did this work before? N/A 

Chrome version: 68.0.3440.84  Channel: stable
OS Version: 
Flash Version:
 
Labels: Needs-Triage-M68
Components: Platform>Extensions
Labels: Triaged-ET Target-70 M-70 FoundIn-70 OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Win-10 and Ubuntu 17.10 using chrome reported version #68.0.3440.84 and latest canary #70.0.3516.0. Issue is not seen in OS-Mac.
This is a non-regression issue as it is observed from M60 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
Components: -UI -Platform>Extensions UI>Accessibility>ChromeVox
Triage -> chromevox
Labels: OS-Chrome
Status: WontFix (was: Untriaged)

Sign in to add a comment