Use appropriate target's walker front for expanding iframe node in markup view when we have same-origin iframe targets
Categories
(DevTools :: Inspector, task)
Tracking
(firefox94 fixed)
Tracking | Status | |
---|---|---|
firefox94 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
Details
(Whiteboard: dt-perf-stability-mvp)
Attachments
(3 files)
At the moment, we have a piece of logic in the walker front code to pick up a different walker front to retrieve a node when the node is a remoteFrame (See https://searchfox.org/mozilla-central/rev/1761c710b035d7dc8892dfa8e56589b4e095221f/devtools/client/fronts/walker.js#336-355)
With Bug 1685500, we'll have targets for each document so even children off same-origin iframes should be retrieved by their associated target.
Assignee | ||
Comment 1•3 years ago
|
||
Depends on D125935
Assignee | ||
Comment 2•3 years ago
|
||
This is a similar change to what was done to node actors in the previous patch
of this queue.
Depends on D126064
Assignee | ||
Comment 3•3 years ago
|
||
isRemoteFrame
was used as a way to know if an iframe was tracked by its own target.
Since we can now have dedicated targets for every iframe, we need to check if a given
iframe is tracked by its dedicated target.
Depends on D126804
Comment 7•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8fede56e49dc
https://hg.mozilla.org/mozilla-central/rev/a8809fa08187
https://hg.mozilla.org/mozilla-central/rev/30b0fc1909f5
Assignee | ||
Updated•3 years ago
|
Description
•