Open Bug 1578747 Opened 5 years ago Updated 2 years ago

Enable Fission frame inspection by default in DevTools

Categories

(DevTools :: General, enhancement, P3)

enhancement

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: ochameau, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

Bug 1578745 introduces a preference to enable the inspection of Fission frames, running in distinct processes. This preference is false by default.

This bug will later help track, once we got the bulk of the work done, the few remaining items that are blocking enabling this feature for Nightly audience.
We may followup on enabling this preference on all channels.

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

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: --- → ?

Tracking for 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

Moving old "dt-fission-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: MVP → Future
Whiteboard: dt-fission-reserve → dt-fission-future
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.