[remote-dbg-next] Improve worker debugging workflow
Categories
(DevTools :: about:debugging, enhancement)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
(Blocks 1 open bug)
Details
Follow up to Bug 1505282.
Several issues were raised by a user who tried worker debugging with about:debugging:
- hard to debug workers with wasm
- would like to break (and open about:devtools-toolbox tab) as soon as worker starts
I think those needs will be better served by the Debugger panel directly rather than by opening a dedicated toolbox for the worker. But if that's the case maybe we should hide the webworkers from about:debugging to encourage users to first inspect the Tab where the worker runs and then use the Debugger.
|
||
Comment 2•7 years ago
|
||
would like to break (and open about:devtools-toolbox tab) as soon as worker starts
Pausing on worker creation is a feature request tracked in bug 1545650 (might be the worker panel or handled by a custom entry in the event breakpoints panel, bug 1526079).
hard to debug workers with wasm
Lars, is this still an issue with bug 1523262 and bug 1520698?
|
|
||
Comment 3•7 years ago
|
||
I believe wasm debugging in workers is now possible, after the fix that made the wasm code visible. (I believe I fixed a tricky bug on Android using that functionality.)
|
Reporter | |
Comment 4•6 years ago
|
||
Thanks for the updates Harald and Lars, will close this one as duplicate of bug 1545650.
Description
•