Open Bug 1605157 Opened 4 years ago Updated 2 years ago

Highlight selector when an execution context is set

Categories

(DevTools :: Console, enhancement, P2)

enhancement

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: Honza, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

When JS execution context is changed to non-default (default == top level document) the user should be able to simply notice that so, he/she is aware of where JS expressions are going to be evaluated.

Honza

Whiteboard: dt-fission-m2-mvp
Priority: P3 → P2

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

Fission Milestone: --- → M6

Note that this is partially working but, I am seeing some inconsistencies.

STR:

  1. Open the Browser Toolbox and select the Console panel
  2. Pick a content process from the selector
  3. The drop down button is grayed out -> BUG, blue background should be used
  4. Focus another Window to unfocus the drop down -> now the background is blue

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.