Closed
Bug 1641654
Opened 4 years ago
Closed 4 years ago
Refactor mozHTMLAccessible 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)
Now that we have an inner MOXAccessible protocol with attribute getters, setters and actions, we can refactor classes in mozHTMLAccessible.
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 1•4 years ago
|
||
A casualty of this is the ability to change listed attribute names on the fly.
I think this is the right choice in general and doesn't seem to affect VO.
If we run into a case where it does we should reconsider.
Depends on D77335
Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8ce11537db06 Remove NSAccessibility methods from mozHTMLAccessible classes. 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
•