Closed
Bug 1598060
Opened 5 years ago
Closed 5 years ago
Fetch the accessibility and its related fronts (walker, highlighter, etc) via the accessible front rather than from panel's singleton
Categories
(DevTools :: Accessibility Tools, enhancement)
DevTools
Accessibility Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: yzen, Assigned: yzen)
References
Details
Attachments
(2 files)
For now, the whole codebase assumes that the accessibility front is unique.
But with Fission, we will start having more than one. We will still have the one related to the top level tab document, but we will then have one per iframe running in a distinct process.
This change makes it so that we can't be using a static reference to just one accessibility/walker front.
We should rather dynamically retrieve the accessibility/walker front which relates to the current context we are currently inspecting.
See more in bug 1568126
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Updated•5 years ago
|
Keywords: leave-open
|
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Updated•5 years ago
|
Assignee: nobody → yzenevich
Pushed by yura.zenevich@gmail.com: https://hg.mozilla.org/integration/autoland/rev/31aa2f99b452 removing walker actor/front passing as an argument where not necessary. r=rcaliman https://hg.mozilla.org/integration/autoland/rev/894b238d2f50 access accessibility walker front through accessible front wherever possible. r=rcaliman
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/31aa2f99b452
https://hg.mozilla.org/mozilla-central/rev/894b238d2f50
|
|
Assignee | |
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•