Closed Bug 1568822 Opened 5 years ago Closed 4 years ago

Make it possible for the "inspect element" context menu item to select elements also in oop frames

Categories

(DevTools :: Inspector, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1647366

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.

Priority: P3 → P2
Whiteboard: dt-fission
Priority: P2 → P3
Whiteboard: dt-fission → dt-fission-reserve

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.

Depends on: 1588773

Tracking Fission DevTools bugs for Fission Nightly (M6)

Fission Milestone: --- → M6

dt-fission-reserve bugs do not need to block Fission Nightly (M6).

Fission Milestone: M6 → ---

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.

Added a test in Bug 1647366, can't really find the exact Bug that added the feature, but closing this one as duplicate.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Whiteboard: dt-fission-reserve
You need to log in before you can comment on or make changes to this bug.