Temporary addon content script does not show up in the Debugger on domains specified by manifest.json
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
People
(Reporter: posilejte.spam, Unassigned)
References
(Blocks 3 open bugs)
Details
Attachments
(3 files)
10.29 KB,
application/x-zip-compressed
|
Details | |
![]() 1.07 MB,
image/png
|
Details | |
48.66 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
Load my temporary addon (the addon src is attached) in about:debugging
Go to a link where a content script of the extension should run: https://www.youtube.com/watch?v=HuIb3XTQVJw
Open developer tools (f12)
Look for the script being listed in the Debugger
Actual results:
In Firefox 96.0b6 (Developer Edition) the script doesn't appear in the Debugger.
Note I used the same addon in both browsers.
Expected results:
In Firefox 95.0 (release) the script appears in the Debugger
Reporter | ||
Comment 1•3 years ago
|
||
Reporter | ||
Comment 2•3 years ago
|
||
Also please note that I installed Firefox Developer Edition an hour ago, so the profile is new
Reporter | ||
Comment 3•3 years ago
|
||
Reporter | ||
Comment 4•3 years ago
|
||
Hopefully it is clear that Firefox 95 displays the script correctly whereas Firefox Developer Edition does not
Comment 5•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 6•3 years ago
|
||
The severity field is not set for this bug.
:Honza, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 7•3 years ago
|
||
Thank you for the report!
I can't see any script in the Debugger that would be loaded from the extension.
Alex, what could be wrong here?
Honza
Updated•3 years ago
|
Updated•2 months ago
|
Comment 8•2 months ago
|
||
Many things were fixed around content script in latest version of Firefox Nightly (Firefox 136).
Would you mind giving it a try again? It works for me when testing the attached addon.
You should see a new menu in the debugger source list, with a "show content scripts" item.
(this is wired to devtools.debugger.show-content-scripts
preference if you prefer the about:config way)
Reporter | ||
Comment 9•2 months ago
|
||
(In reply to Alexandre Poirot [:ochameau] from comment #8)
Many things were fixed around content script in latest version of Firefox Nightly (Firefox 136).
Would you mind giving it a try again? It works for me when testing the attached addon.
You should see a new menu in the debugger source list, with a "show content scripts" item.
(this is wired todevtools.debugger.show-content-scripts
preference if you prefer the about:config way)
It works now, when I set devtools.debugger.show-content-scripts
to true
, I saw the attached temporary addon, as well as all permanently installed addons.
Each addon appears in its own category (same icon as main thread), to mark that it is a separate process (unlike when the bug was filed), right?
Inside that category, the content scripts are shown correctly :)
Reporter | ||
Comment 10•2 months ago
|
||
However now in that UI, there is a weird behaviour, where there are duplicated addon entries (permanent addons). Either Dark Reader is launched in more processes, or it is a bug. See picture
Description
•