Closed Bug 1473168 Opened 7 years ago Closed 7 years ago

Web Extension sources collision in Debugger

Categories

(DevTools :: Debugger, defect)

Product:
DevTools
Component:
Debugger
Version:
60 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ris58h, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180607190419 Steps to reproduce: 1. Install two or more different Web Extensions. Each of them must contain a content-script with the same name. 2. Open Developer Console on a page where it's possible. 3. Go to Debugger -> Sources -> moz-extension:// 4. Open the content-script. Actual results: Only one (random?) content-script is opened. Expected results: There should be a way to open each content-script. May be 'moz-extension://' tree-item should contain sub-item for each extension.
Actually there is a way to open both (in my case) content-scripts in Debugger: 1. Open the (random?) content-script. It will create a tab with a script's content. 2. Close debugger. 3. Open it the content-script again. It will create a second tab with a second script's content.
Hi ris58h, can you please give me a few concrete examples of Web Extensions that you used to reproduce this issue?
Flags: needinfo?(ris58h)
Of course. I use those: https://addons.mozilla.org/en-US/firefox/addon/make-medium-readable-again/ https://addons.mozilla.org/en-US/firefox/addon/youtube-tracks/ They both have content.js file inside.
Flags: needinfo?(ris58h)
Thank you for the help! I managed to reproduce the issue on [Ubuntu 16.04] Firefox 60.0 and 61.0.1. It is not reproducing for me on Firefox 62.0b6 and Nightly 63.0a1 (2018-07-09). Can you please also try to download the latest Nightly and try to reproduce the issue? You can download it from here: https://download.mozilla.org/?product=firefox-nightly-latest-ssl&os=linux64&lang=en-US
Status: UNCONFIRMED → NEW
Component: Untriaged → Debugger
Ever confirmed: true
Flags: needinfo?(ris58h)
Product: Firefox → DevTools
I've checked it for Nightly 63.0a1 and it works without problems. One thing I would like to have it's a meaningful naming for extensions in the debugger. Shall I create another issue?
Flags: needinfo?(ris58h)
In this case, I am closing the issue as Resolved WFM. For the naming that you proposed, yes, please create another issue and set the Importance to: Enhancement. Thank you!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.