Can't open a Multiprocess Toolbox from about:debugging when connected to an older server
Categories
(DevTools :: Framework, defect, P3)
Tracking
(firefox-esr102 unaffected, firefox108 unaffected, firefox109 unaffected, firefox110 fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox108 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: jdescottes)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Steps to reproduce
- Start an older server (e.g.
/Applications/Firefox.app/Contents/MacOS/firefox --start-debugger-server 6081
) - On Nightly, go to about:debugging and connect to the older server
- On the "Process" section, there should be "Multiprocess Toolbox" and an "inspect" button, click on it
Expected results
A toolbox opens in a new tab
Actual results
A tab is added but it is blank.
The following error is thrown:
console.error: "Exception while opening the toolbox" "Error: Unsupported target type 'frame'" (new Error("Unsupported target type 'frame'", "resource://devtools/shared/commands/target/target-command.js", 500))
startListening@resource://devtools/shared/commands/target/target-command.js:500:15
async startListening({ isTargetSwitching = false } = {}) {
...
// Only a few top level targets support the watcher actor at the moment (see WatcherActor
// traits in the _form method). Bug 1675763 tracks watcher actor support for all targets.
if (this.hasTargetWatcherSupport(type)) {
...
} else {
throw new Error(`Unsupported target type '${type}'`);
}
Assignee | ||
Comment 1•2 years ago
|
||
Probably a recent regression. Works fine from DevEdition and worked fine before updating my Nightly.
Assignee | ||
Comment 2•2 years ago
•
|
||
Ah it seems to only happen when switching to multiprocess, devtools.browsertoolbox.scope
= "everything"
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Older servers still need the boolean isBrowserToolboxFission for getWatcher/getTarget.
Comment 4•2 years ago
|
||
Set release status flags based on info from the regressing bug 1625939
Comment 6•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Description
•