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

Issue 835115 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
OOO until 4th Feb
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Whitelist accessibilityFeatures.read API for Secure Shell

Project Member Reported by raymes@chromium.org, Apr 20 2018

Issue description

We're working on adding accessibility support to Secure Shell (see  issue 822490 ). Having good accessibility support will result in a performance loss so we want to detect when spoken feedback is enabled. This requires the chrome.accessibilityFeatures.spokenFeedback.get() API which needs the accessibilityFeatures.read permission. However, for various reasons that are difficult to address, Secure Shell is stuck as a "v1.5" chrome app, whereas the accessibilityFeatures API is only available to v2.0 apps.

As a workaround, we'd like whitelisted access to FSP from Secure Shell for the following app ids:

Secure Shell Stable: pnhechapfaindjhompbnflcldabbghjo
Secure Shell Dev: okddffdblfhhnmhodogpojmfkjmhinfp

 

Comment 1 by vapier@chromium.org, Jun 17 2018

Cc: vapier@chromium.org
Components: Platform>Apps>Default>Hterm

Comment 2 by raymes@chromium.org, Jun 18 2018

Status: Fixed (was: Assigned)
Fixed in https://chromium-review.googlesource.com/1018500 

Sign in to add a comment