Open Bug 1605173 Opened 5 years ago Updated 2 years ago

JS execution context selector should indicate paused threads

Categories

(DevTools :: Console, enhancement, P2)

Product:
DevTools
Component:
Console
Type:
enhancement

Tracking

(Fission Milestone:Future)

Project Flags:
Fission Milestone Future

People

(Reporter: Honza, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

Thread listed in the Context Selector should indicate paused state the same way as the Threads panel does it. This will allow the user to simply see what threads are paused (directly from within the selector itself).

The visual representation of threads in the Selector drop down should be the same as in the Threads side panel in the Debugger (ideally share the same code path).

Honza

Priority: P3 → P2

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

Fission Milestone: --- → M6

As soon as implemented it can be nicely tested using STRs from bug 1605162 comment #2

Honza

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

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

Fission Milestone: M7 → MVP
Whiteboard: dt-fission-m2-reserve → 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
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.