Open Bug 1620252 Opened 5 years ago Updated 2 years ago

Check if we can find something better than "Top" for the context selector label

Categories

(DevTools :: Console, task, P3)

Product:
DevTools
Component:
Console
Type:
task

Tracking

(Fission Milestone:Future)

Project Flags:
Fission Milestone Future

People

(Reporter: nchevobbe, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

From my experience, "Top" is vague and I'm not sure it would mean something for a lot of people.

We should think of something more straightforward for this label so users can understand it right away.

Also, after Bug 1605166 lands, selecting the Main Thread in the debugger would select Top in the console context selector, which can be a bit confusing (you have to do the mental mapping yourself)

Component: Framework → Console
Priority: -- → P2

Tracking Fission DevTools bugs for Fission Nightly (M6) milestone

Fission Milestone: --- → M6
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

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.