Closed
Bug 1811257
Opened 2 years ago
Closed 2 years ago
Browser toolbox's debugger stays empty as soon as you start using the iframe dropdown
Categories
(DevTools :: Debugger, defect, P2)
DevTools
Debugger
Tracking
(firefox111 fixed)
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
Details
Attachments
(1 file)
STR:
- open the browser toolbox on the debugger
- use the iframe dropdown to select any other parent process document
The debugger will be empty, even if you move back to browser.xhtml.
Assignee | ||
Comment 1•2 years ago
|
||
Similarly to WebExtension, the browser toolbox is still using the non-EFT codepath
when moving between "iframes". This forces us to use the same trick
and force updating source-tree's thread attribute on each navigation.
A fake navigation is dispatched when navigating between iframes via the dropdown.
Also, it isn't clear if the old legacy listener codepath was forcing to refetch
the sources, but we miss something in the SOURCES resource watcher to register
again all sources of the new selected iframe.
Updated•2 years ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/316aee76614c
[devtools] Fix browser toolbox debugger source tree when using the iframe dropdown. r=devtools-reviewers,jdescottes
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•