Closed
Bug 1944107
Opened 7 months ago
Closed 5 months ago
Allow instantiating content script targets when session context is of all type
Categories
(DevTools :: Framework, enhancement)
DevTools
Framework
Tracking
(firefox137 fixed)
RESOLVED
FIXED
137 Branch
Tracking | Status | |
---|---|---|
firefox137 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
VS Code adapter would benefit from using the same codepath as the browser toolbox.
i.e. Using a Watcher actor whose session context type is set to "all" and debugging everything it all processes.
But for now, the multiprocess browser toolbox doesn't need to spawn the content script targets.
Content scripts sources are currently returned by the Content Process target of the process where the script runs.
As VS.Code only cares about web pages and content scripts, it is not using the content process target and so would benefit from using the content script targets.
Assignee | ||
Comment 1•7 months ago
|
||
Updated•6 months ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/782e9a5834e8
[devtools] Instantiate Content Script targets when debugging all contexts. r=devtools-reviewers,hbenl,bomsy
Comment 3•5 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•