Firefox should have a new menu item to open "about:debugging#addons" page
Categories
(DevTools :: about:debugging, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: kernp25, Unassigned)
References
Details
Attachments
(1 obsolete file)
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Comment 4•5 years ago
|
||
ccing Harald,
Even though this request was for the old about:debugging I think it would still be valid with the new one.
We could have a "Debug extensions" or "Extensions" menu item pointing to about:debugging#/runtime/this-firefox
Comment 5•5 years ago
|
||
In line with other menu items would be "Add-on Debugging" – or "Extension Debugging" aligned with the copy used in about:add-ons and remote debugging
Philip, is this additional entry point something you would think to be helpful for extension developers to get started or return to debugging?
Comment 6•5 years ago
|
||
I would even go so far to suggest that the "This Firefox" section should be shown by default when going to about:debugging . I think this is mainly a devtools product decision, but to my mind when debugging on Firefox Desktop, the defaults should show debugging for the device you are on and not potential devices you could connect to.
Either way, a quick and easy way to reach the debugging for extensions for the currently used browser would be beneficial for extension developers. I would go with "Extension Debugging", and maybe add a separator after all the different debugging and toolbox options.
Comment 7•5 years ago
|
||
I would even go so far to suggest that the "This Firefox" section should be shown by default when going to about:debugging
Makes sense. The redesign has focused on migrating WebIDE workflows which probably skewed the design towards that, to make GeckoView an easy target for devs. Another assumption was that there are mobile web developers than extension developers – but we also assumed that we have to drive more devs to GeckoView to show that in actual remote debugging usage numbers.
I'd propose to track usage numbers for each section (already landed) and adjust sections accordingly.
Either way, a quick and easy way to reach the debugging for extensions for the currently used browser would be beneficial for extension developers. I would go with "Extension Debugging", and maybe add a separator after all the different debugging and toolbox options.
SGTM. I suggest keeping it P3 as we have not gotten many requests and it depends somewhat on the section re-sorting.
Updated•2 years ago
|
Updated•7 months ago
|
Description
•