New issue
Advanced search Search tips

Issue 607940 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 7
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-09-07
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility

Blocking:
issue 647835



Sign in to add a comment

Extension prompt for new permissions not accessible during extension upgrade

Project Member Reported by dtseng@chromium.org, Apr 29 2016

Issue description

STR
- push a ChromeVox update
- restarting the browser, Chrome prompts the user for re-enabling an extension that has requested more permissions
(ChromeVox has not requested new permissions in some time)*
- the permission bubble isn't accessible (because ChromeVox is not actually enabled).

expected:
- the permissions upgrade check appears to be broken (ChromeVox doesn't actually request perms)

1. The permissions check logic appears to be wrong or unexpectd. Requires investigation.
2. Orca should be accessible with Chrome

Note that this isn't really an issue on Mac/Windows, because other screen readers come into play.
 
Components: Platform>Extensions UI>Accessibility
Cc: treib@chromium.org rdevlin....@chromium.org mea...@chromium.org
Which version of chrome are you running, and when did you see this?

The permission warning prompt sounds vaguely like  crbug.com/603822 , but it doesn't look like ChromeVox has notifications permission, which we think is the only one that would cause that.

I also wonder if ChromeVox should be exempt from the normal upgrade flow, since it is so important for many users that have it installed.  Unfortunately, I'm not sure we can completely exempt it.  +meacer for his thoughts.

Also, what is "orca"?
Labels: Needs-Feedback
Status: Available (was: Untriaged)
ping dtseng - can you respond to the questions in comment 2?

Blocking: 647835
Labels: NewComponent-Accessibility NewComponent-Accessibility-ChromeVox
Components: UI>Accessibility>ChromeVox
Labels: -newcomponent-accessibility -newcomponent-accessibility-chromevox
Components: -UI>Accessibility
Project Member

Comment 8 by sheriffbot@chromium.org, Apr 23 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: OS-Chrome
NextAction: 2018-09-07
Do we know if this is still an issue with the latest UIs?
The NextAction date has arrived: 2018-09-07
Status: Archived (was: Untriaged)
Archiving for now due to lack of activity, but please reopen if this is still an issue!

Sign in to add a comment