Enable Context Selector in Nightly
Categories
(DevTools :: Framework, task, P2)
Tracking
(Fission Milestone:Future, firefox-esr91 wontfix, firefox94 wontfix, firefox95 wontfix, firefox96 fixed)
People
(Reporter: Honza, Assigned: nchevobbe)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-future, dt-perf-stability-mvp)
Attachments
(1 file, 1 obsolete file)
Let's enable the Context Selector for Nightly users when ready for testing.
Pref:
devtools.webconsole.input.context
Honza
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
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
Comment 3•5 years ago
|
||
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.
Comment 4•5 years ago
|
||
Tracking dt-fission-m2-mvp bugs for Fission Nightly milestone (M6c)
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
(moving to reserve as it's not critical for fission m2 and we might need the slot for mvp work)
Updated•5 years ago
|
Comment 6•4 years ago
|
||
Bulk move of all dt-fission-m2-reserve bugs to Fission MVP milestone.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 9•3 years ago
|
||
We take this opportunity to merge the browser toolbox and content toolbox preferences
into a single one.
Depends on D131600
Updated•3 years ago
|
Comment 10•3 years ago
|
||
Comment 11•3 years ago
|
||
bugherder |
Comment 12•3 years ago
|
||
Backed out for causing damp failures.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | damp | inspector/custom.js: Test timed out
Assignee | ||
Updated•3 years ago
|
Comment 13•3 years ago
|
||
Comment 14•3 years ago
|
||
bugherder |
Comment 15•3 years ago
|
||
Setting status-firefox95=wontfix because we don't need to uplift the Context Selector to Beta 95.
Description
•