Closed
Bug 1388885
Opened 7 years ago
Closed 7 years ago
Developer Tools fails to find WebExtensions Add-on sources
Categories
(WebExtensions :: Developer Tools, defect, P1)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1346902
People
(Reporter: demonfiddler, Assigned: rpl)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170628075643 Steps to reproduce: I am in the process of porting my Random Walk Add-on (https://addons.mozilla.org/en-US/firefox/addon/random-walk/) from the Add-on SDK to WebExtensions. (I have ported the Add-on to a mostly working state but not yet pushed any changes to GitHub - I could attach sources if asked.) Steps: 1. about:debugging#addons > Load Temporary Add-on > Random Walk manifest.json 2. about:debugging#addons > Random Walk > Debug 3. Accept the 'Incoming Connection' dialog -OR- 4. about:debugging#addons > Random Walk > Refresh Actual results: More often than not when I hit the Debug button the Developer Tools window fails to find the main background script (lib/main.js), showing instead the message "This page has no sources". Sometimes it does show main.js immediately after hitting Debug; sometimes it shows other background scripts such as (my local) common.js or options.js but not main.js. It never shows any sources when I hit Reload. Expected results: The Developer Tools window > Sources pane should list all the Add-on's background scripts.
Reporter | ||
Comment 1•7 years ago
|
||
I omitted to mention that when the "This page has no sources" message is displayed, the console log nevertheless contains log messages emitted by the invisible background script but when I click on the main.js link to the right of the log message, the window opened by this action comes up blank.
Reporter | ||
Comment 2•7 years ago
|
||
Also, I can now see that when the Developer Tools window opens following a click on the Debug button, the names of the common.js and main.js are displayed fleetingly before being replaced by the "This page has no sources" message.
Updated•7 years ago
|
Component: Untriaged → WebExtensions: General
Product: Firefox → Toolkit
Updated•7 years ago
|
Component: WebExtensions: General → WebExtensions: Developer Tools
Assignee | ||
Comment 3•7 years ago
|
||
On Firefox 54 the debugger UI used by the Addon Debugging tools is still the old one and this was a known issue on that version of the debugger UI, are you able to reproduce the same issue with a more recent version of Firefox which uses the new debugger UI? (e.g. Firefox 55 which is the new released version or using the beta or nightly version) You can recognize the new debugger UI by looking at this screenshots from MDN: - https://developer.mozilla.org/en-US/docs/Tools/Debugger/UI_Tour
Flags: needinfo?(demonfiddler)
Assignee | ||
Updated•7 years ago
|
Priority: -- → P1
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → lgreco
Reporter | ||
Comment 4•7 years ago
|
||
I just updated to FireFox 55.0.2, where the problem seems to have been resolved. Thanks all for your comments.
Flags: needinfo?(demonfiddler)
Assignee | ||
Comment 5•7 years ago
|
||
Thanks for the confirmation. I'm going to close this bug as a duplicate of Bug 1346902 (which is the one that has enabled the new debugger UI in the Browser Toolbox and the Addon Debugging Toolbox)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•