[remote-dbg-next] Stop using the Browser Toolbox to debug local addons
Categories
(DevTools :: about:debugging, enhancement, P1)
Tracking
(firefox67 fixed)
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: jdescottes, Assigned: daisuke)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
webextensions are now running out of process, so in theory we can now debug them using a regular toolbox rather than a browser toolbox.
My current issues with using the browser toolbox are:
- it is slower to open
- only one can be opened at a time
- it uses confusing profile settings for addon developers
- it prevents from having a unified debugging UX in about:debugging, where we could in theory debug everything with about:devtools-toolbox tabs.
- it forces to enable remote debugging to debug local addons. We also have to maintain a UI for this in about:debugging ("enable addon debugging" checkbox)
If we stop using the browser toolbox, we will however have to rewrite our current mochitests that assert debugging webextensions.
In the future, we want to list processes in about:debugging as well. If we want to stop using the Browser Toolbox, it means we won't be able to debug the Main Process for this-firefox, but I think this limitation is acceptable.
This relates to the overall issue of about:debugging having too many inconsistent workflows (toolbox in a tab, toolbox in a window, toolbox in a new firefox instance). Another way to tackle this would be to go the opposite way and use the Browser Toolbox for everything. We should discuss pros and cons of both strategies.
|
Reporter | |
Updated•6 years ago
|
|
Assignee | |
Updated•6 years ago
|
|
|
Assignee | |
Comment 3•6 years ago
|
||
|
|
Assignee | |
Comment 4•6 years ago
|
||
Depends on D20786
|
||
Comment 6•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/6dadc0b70109
https://hg.mozilla.org/mozilla-central/rev/9cc065c29f51
Description
•