Make it possible for the "inspect element" context menu item to select elements also in oop frames
Categories
(DevTools :: Inspector, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: pbro, Unassigned)
References
(Blocks 1 open bug)
Details
With fission, certain parts of web pages might run in other processes than the parent page.
The browser context menu item "Inspect Element" must continue to work in this situation.
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 1•5 years ago
|
||
With the work from Bug 1588773, the Inspect Element feature will start relying on contentDOMReference which means we can use a similar logic as what was done for converting grips to nodefronts: contentDOMReference includes the browsingContextId, so this can be leveraged to retrieve the good walker front.
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Tracking Fission DevTools bugs for Fission Nightly (M6)
Comment 3•4 years ago
|
||
dt-fission-reserve bugs do not need to block Fission Nightly (M6).
Comment 4•4 years ago
|
||
I think this is already working at the moment, with fission.autostart
and devtools.contenttoolbox.fission
, I can use "inspect element" on Elements living inside of oop frames. We might only be missing a test here.
Comment 5•4 years ago
|
||
Added a test in Bug 1647366, can't really find the exact Bug that added the feature, but closing this one as duplicate.
Updated•4 years ago
|
Description
•