Closed
Bug 1641655
Opened 4 years ago
Closed 4 years ago
Refactor mozSelectableElements classes to use MOXAccessible API
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla78
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
(Whiteboard: [mac2020_1])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Now that we have an inner MOXAccessible protocol with attribute getters, setters and actions, we can refactor classes in mozSelectableElements.
|
Assignee | |
Comment 1•4 years ago
|
||
A casualty of this is the "switch" action description for pressing tabs. That code
goes way back to our first Mac a11y support. WebKit and Chromium don't have it.
I tried to figure out when other browsers or apps had that with no luck.
Anyway, removing that description gives us the same behavior in VO as
WebKit and Chromium where there are no custom action description strings.
Depends on D77341
Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ac961c753915
Remove NSAccessibility methods from mozSelectableElements. r=morgan
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
|
|
Assignee | |
Updated•4 years ago
|
Priority: P2 → P1
You need to log in
before you can comment on or make changes to this bug.
Description
•