Closed Bug 1587099 Opened 5 years ago Closed 3 years ago

Make the node-picker work with real fission iframes and add a new mochitest for it

Categories

(DevTools :: Inspector, task, P3)

task

Tracking

(Fission Milestone:MVP)

RESOLVED DUPLICATE of bug 1607756
Fission Milestone MVP

People

(Reporter: pbro, Unassigned)

References

(Blocks 1 open bug)

Details

Once bug 1574401 lands, we'll have a node-picker that works with remote <browser> frames in the browser toolbox.

That's a great start, but for it to work for real with fission iframes in content documents, we will need to (at least) change this function so it returns true for remote content iframes too.

And once done, we should also add a new mochitest to check that this works for real.
For the browser toolbox case, we couldn't really add a mochitest, so this new node-picker ability is not currently covered by tests.

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

Blocks enabling Fission in Nightly (M6)

Fission Milestone: ? → M6

dt-fission-reserve bugs do not need to block Fission Nightly (M6), but these bugs' summaries mention the word "Fission", so let's track them for Fission riding the trains to Beta (M7). We'll revisit these bugs before we ship Fission.

Fission Milestone: M6 → M7

Tracking dt-fission-reserve bugs for Fission MVP until we know whether they really need to block Fission or not.

Fission Milestone: M7 → MVP

Solved by Bug 1607756

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