Closed
Bug 1605757
Opened 6 years ago
Closed 5 years ago
Decouple accessibility front from the client code as much as possible.
Categories
(DevTools :: Accessibility Tools, task, P1)
DevTools
Accessibility Tools
Tracking
(Fission Milestone:M6, firefox75 fixed)
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: yzen, Assigned: yzen)
References
Details
(Whiteboard: dt-fission-m2-reserve)
Attachments
(1 file)
Right now we are passing accessibility front directly to the ui components to be used in enable/disable actions and also to listen to some accessibility events.
We should instead pass a function that will enable/disable accessibility since lifecycle functionality will need to be handled differently for fission.
Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Assignee: nobody → yzenevich
Status: NEW → ASSIGNED
Updated•6 years ago
|
Whiteboard: dt-fission-m2-mvp
Updated•6 years ago
|
Priority: -- → P1
Whiteboard: dt-fission-m2-mvp → dt-fission-m2-mvp
Comment 2•6 years ago
|
||
Tracking DevTools bugs for Fission Nightly (M6) milestone
Fission Milestone: --- → M6
Updated•6 years ago
|
Whiteboard: dt-fission-m2-mvp → dt-fission-m2-reserve
Pushed by yura.zenevich@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/53f21efd04f2
decouple accessibility front front the accessibility panel UI. r=rcaliman
Comment 4•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 75
You need to log in
before you can comment on or make changes to this bug.
Description
•