Closed
Bug 1808576
Opened 1 year ago
Closed 1 year ago
Remove support of spawning toolboxes to debug content processes via about:devtools-toolbox URLs
Categories
(DevTools :: General, task)
DevTools
General
Tracking
(firefox110 fixed)
RESOLVED
FIXED
110 Branch
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
This feature isn't really meant to be supported. It was a way to spawn a browser content toolbox. But this feature has been recently removed in bug 1593753.
|
Assignee | |
Comment 1•1 year ago
|
||
We are consolidating the different types of toolbox configurations we support.
Content processes should be debugged via the Multiprocess Browser Toolbox.
|
||
Updated•1 year ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•1 year ago
|
||
This was mostly meant to be used by the Browser Content Toolbox
which has been recently removed.
We should no spawn a commands which is focusing only on a given content process.
Instead a main process commands should be used and targets will be exposed for each content process.
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/824c72619da7 [devtools] Remove support for debugging content process via about:devtools-toolbox URL. r=jdescottes https://hg.mozilla.org/integration/autoland/rev/9bd1a2aecf37 [devtools] Remove CommandsFactory.forProcess. r=jdescottes
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/824c72619da7
https://hg.mozilla.org/mozilla-central/rev/9bd1a2aecf37
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•