Selecting a source in a content process can be confusing
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Fission Milestone:Future)
Fission Milestone | Future |
People
(Reporter: jlast, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-future)
Attachments
(2 files)
STR:
- open browser toolbox with fission enabled
- expand several content process directories
- select ContextMenuChild.jsm in one of the the processes
NOTE: that the first source in the tree will be selected.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Note about the STRs, make sure to right click in different tabs in order to load ContextMenuChild in the various content processes.
Comment 2•5 years ago
|
||
Hmmm, I noticed the same thing without Fission enabled.
STR:
1.Open http://dbg-workers.glitch.me/
2.Expand directories.
3.Click util.js
and worker.js
in the first worker in source panel to open files in editor.
4.Click util.js
and worker.js
in the second worker in source panel.
Let me know if I'd better open a bug that will be not fission related.
Reporter | ||
Comment 4•5 years ago
|
||
Thanks Chujun, I think it is fine to solve it in the worker scenario. I think it will will work in both cases.
Comment 5•5 years ago
|
||
Tracking Fission DevTools bugs for Fission Nightly (M6)
Comment 6•5 years ago
|
||
dt-fission-reserve bugs do not need to block Fission Nightly (M6).
Comment 7•4 years ago
|
||
Tracking dt-fission-reserve bugs for Fission MVP until we know whether they really need to block Fission or not.
Comment 8•4 years ago
|
||
Moving old "dt-fission-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.
Comment 9•3 years ago
|
||
The debugger works much better now with sources having the same URL from distinct threads.
Description
•