Closed Bug 1598011 Opened 5 years ago Closed 4 years ago

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

Categories

(DevTools :: Accessibility Tools, enhancement, P3)

enhancement

Tracking

(Fission Milestone:M7)

RESOLVED FIXED
Fission Milestone M7

People

(Reporter: yzen, Unassigned)

References

Details

With fission, certain parts of web pages might run in other processes than the parent page.
The browser context menu item "Inspect Accessibility Properties" must continue to work in this situation.

Fission Milestone: --- → M6

Blocks enabling Fission in Nightly (M6).

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

dt-fission-m2-reserve bugs do not need to block Fission Nightly (M6). For now, let's track them for Fission riding the trains to Beta (M7) so we revisit these bugs before we ship Fission.

Fission Milestone: M6 → M7

I think this is already working at the moment, with fission.autostart and devtools.contenttoolbox.fission, I can use "Inspect Accessibility Properties" on Elements living inside of oop frames. We might only be missing a test here.

(In reply to Julian Descottes [:jdescottes] from comment #3)

I think this is already working at the moment, with fission.autostart and devtools.contenttoolbox.fission, I can use "Inspect Accessibility Properties" on Elements living inside of oop frames. We might only be missing a test here.

Yes, this has been fixed recently. Tests are going to be added in a separate bug.

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