Don't listen for shared worker targets in content toolbox.
Categories
(DevTools :: Framework, task)
Tracking
(firefox81 fixed)
| Tracking | Status | |
|---|---|---|
| firefox81 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
Details
Attachments
(1 file)
Support for SharedWorker debugging in the content toolbox will be handled in Bug 1607778.
But the LegacySharedWorkerWatcher doesn't do any check, and ends up calling listWorkers (devtools/server/actors/targets/browsing-context.js#747), which will end up creating a WorkerTargetListActor (browsing-context.js#731,733-736,754), where we only watch for dedicated workers.
Having that being triggered as part of the SharedWorker listener in content toolbox can cause trouble, especially if/when we listen for dedicated worker targets by other means than the WorkerTargetListActor (like in Bug 1633712).
| Assignee | ||
Comment 1•5 years ago
|
||
Support for SharedWorker debugging in the content toolbox will be handled in Bug 1607778.
But the LegacySharedWorkerWatcher doesn't do any check, and ends up calling listWorkers
on the browsing context target actor, which creates a WorkerTargetListActor
where we only care about dedicated worker.
Having that being triggered as part of the SharedWorker listener in content toolbox
can cause issues, especially if/when we listen for dedicated worker targets by
other means than the WorkerTargetListActor (like in Bug 1633712).
Comment 3•5 years ago
|
||
| bugherder | ||
Description
•