Open Bug 1605330 Opened 2 years ago Updated 2 months ago

Enable Context Selector in Nightly

Categories

(DevTools :: Framework, task, P2)

task

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: Honza, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future, dt-perf-stability-mvp)

Attachments

(1 obsolete file)

Let's enable the Context Selector for Nightly users when ready for testing.

Pref:
devtools.webconsole.input.context

Honza

Fission Milestone: --- → M6
Assignee: nobody → jlaster
Status: NEW → ASSIGNED
Priority: P2 → P1

Let's block this one on the following for now

  • Worker support
  • Remote frame support

We can reevaluate when one of those is ready (the support for remote frames might be done first)

Honza

Depends on: 1624873

Bug 1593937 is going to help keep the list of frame target up to date. Otherwise, the selector would only show already existing targets, and not the one created after the toolbox is opened.
So we should probably review the state of the selector after bug 1593937 is landed. This might highlight some other limitation.

Regarding workers, we could as well decide that we do not care about displaying workers yet?
In this case, it means that we should probably introduce another preference in bug 1592584 so that we enable worker targets in content toolbox only once everything works great around them.

Finally, we might want to block on bug 1602748. Otherwise, we would only display remote frames in the selector. i.e. frames which are loaded in a distinct process from their parent document. i.e. frame using a distinct domain from their parent document. Bug 1602748 is only about introducing a preference, this will most likely require more work before being enable to turn this on by default and depends on completing M2 milestone.

Depends on: 1593937

Tracking dt-fission-m2-mvp bugs for Fission Nightly milestone (M6c)

Fission Milestone: M6 → M6c
Attachment #9139233 - Attachment is obsolete: true

(moving to reserve as it's not critical for fission m2 and we might need the slot for mvp work)

Whiteboard: dt-fission-m2-mvp → dt-fission-m2-reserve
Assignee: jlaster → nobody
Status: ASSIGNED → NEW

Bulk move of all dt-fission-m2-reserve bugs to Fission MVP milestone.

Fission Milestone: M6c → MVP
Whiteboard: dt-fission-m2-reserve → dt-fission-m3-mvp
Whiteboard: dt-fission-m3-mvp → dt-fission-m3-reserve

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

Fission Milestone: MVP → Future
Whiteboard: dt-fission-m3-reserve → dt-fission-future
Priority: P1 → P2
Whiteboard: dt-fission-future → dt-fission-future, dt-perf-stability-triage
Depends on: 1685500
Whiteboard: dt-fission-future, dt-perf-stability-triage → dt-fission-future, dt-perf-stability-mvp
You need to log in before you can comment on or make changes to this bug.