Closed
Bug 1715911
Opened 3 years ago
Closed 3 years ago
Use DOCUMENT_EVENT's dom-complete event in the DOM panel
Categories
(DevTools :: DOM, task)
DevTools
DOM
Tracking
(Fission Milestone:M8, firefox91 fixed)
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
The DOM panel is still using the target event and should use the resource instead, which is more resilient with cross process navigation.
Assignee | ||
Updated•3 years ago
|
Summary: Use DOCUMENT_EVENT's navigate event in the DOM panel → Use DOCUMENT_EVENT's dom-complete event in the DOM panel
Assignee | ||
Comment 1•3 years ago
|
||
This slightly change panel initialization,
instead of updating the UI on opening as soon as the first top level target is available,
it will only update once the navigate resource fires.
So if we open the toolbox on a still loading document, it will update later, but only once
instead of twice.
Updated•3 years ago
|
Fission Milestone: --- → M8
Whiteboard: dt-fission-m3-triage → dt-fission-m3-mvp
Updated•3 years ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6d23df924a53
[devtools] Use DOCUMENT_EVENT's dom-complete event in the DOM panel r=nchevobbe
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•