Debugging support for Shared Workers
Categories
(DevTools :: Debugger, enhancement, P5)
Tracking
(Not tracked)
People
(Reporter: Harald, Unassigned)
References
(Blocks 1 open bug)
Details
User Story
When debugging shared workers, I want to see them in the threads panel, so that I can debug them.
Attachments
(4 files)
Test page: http://mdn.github.io/simple-shared-worker/
Comment 1•6 years ago
|
||
This patch shows shared workers in the debugger's threads pane, if the new devtools.debugger.features.windowless-shared-workers preference is set.
This is pretty straightforward, but there is a question here of which shared workers should be shown in the debugger. Unlike service workers, tabs have to explicitly connect with a shared worker by creating it, but information about these connections isn't exposed in IDLs as far as I can see. This patch avoids this issue by showing all shared workers that are same-origin with the tab being debugged, similar to what we do with service workers. This should give a pretty good result while avoiding difficulties managing the state around which tabs are connected to which shared workers.
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Depends on D59640
Comment 4•6 years ago
|
||
Depends on D59641
Reporter | ||
Comment 5•6 years ago
|
||
Honza: Not sure how bad bitrot will be here and how much work is still needed. Could you assess if we should park it for later or give it the nudge it needs now?
Comment 6•5 years ago
|
||
Baku, would you know if we can/how hard it would be to expose the windows a given SharedWorker lives in, in the WorkerDebugger ?
The idea would be able to properly display the shared worker in the debugger and in the console evaluation context selector, in the content toolbox.
Comment 7•5 years ago
|
||
We could expose the list of window IDs. Is it enough?
Comment 8•5 years ago
|
||
yeah, I think that it would be great
Comment 9•5 years ago
|
||
Asuth, is it something you (or the worker/storage team) have time to work on?
Comment 10•5 years ago
|
||
Yes, I file bug 1657130 to cover implementing this and will share it at our team meeting today.
Comment 11•5 years ago
|
||
Nicolas, Andrew, thanks for helping with this one!
Updated•3 years ago
|
Description
•