Closed Bug 1715909 Opened 3 years ago Closed 3 years ago

Use DOCUMENT_EVENT's dom-complete event in the accessibility panel

Categories

(DevTools :: Accessibility Tools, task)

task

Tracking

(Fission Milestone:M8, firefox91 fixed)

RESOLVED FIXED
91 Branch
Fission Milestone M8
Tracking Status
firefox91 --- fixed

People

(Reporter: ochameau, Assigned: ochameau)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-m3-mvp)

Attachments

(1 file)

The accessibility panel is still using the target event and should use the resource instead, which is more resilient with cross process navigation.

https://searchfox.org/mozilla-central/search?q=%22navigate%22&path=devtools%2Fclient%2Facc&case=false&regexp=false

Summary: Use DOCUMENT_EVENT's navigate event in the accessibility panel → Use DOCUMENT_EVENT's dom-complete event in the accessibility panel

I'm not sure it is useful to hide ResourceCommand in the proxy layer.
It is better if all frontend uses Commands directly, having intermediate layer
make it harder to understand and debug.

Fission Milestone: --- → M8
Whiteboard: dt-fission-m3-triage → dt-fission-m3-mvp
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/38cc602396de
[devtools] Use DOCUMENT_EVENT's dom-complete event in the accessibility panel. r=nchevobbe
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: