New issue
Advanced search Search tips

Issue 695247 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Pass each ax mode to chrome://accessibility independently.

Project Member Reported by dougt@chromium.org, Feb 22 2017

Issue description

In https://cs.chromium.org/chromium/src/content/browser/resources/accessibility/accessibility.js?l=27

we are currently passing the ax mode as an int.  Instead, we should pass flags separately.  This will allow us to remove AccessibilityMode::get() which breaks encapsulation.
 
Labels: NewComponent-Accessibility-Internals NewComponent-Accessibility
Components: Internals>Accessibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-internals -newcomponent-accessibility

Comment 4 by dougt@chromium.org, Apr 25 2017

note that AccessibilityMode::get() is now mode()
Labels: triage-dominic-internals
Labels: -triage-dominic-internals
Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 7 by sheriffbot@chromium.org, Aug 13

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: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)

Sign in to add a comment