Open Bug 1581866 Opened 5 years ago Updated 2 years ago

Debugger does not show webextension source code

Categories

(DevTools :: Debugger, defect, P3)

71 Branch
defect

Tracking

(Not tracked)

People

(Reporter: code, Unassigned)

References

(Blocks 2 open bugs)

Details

Attachments

(4 files)

Attached file reproducer.tar (deleted) —

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Load attached webextension in about:debugging, try to debug it.

Actual results:

Source code is nowhere to be found.

Expected results:

Source code should have been available.

This happens on both FF69 and FF71 and maybe on versions in between, although I didn't bother to check.

Component: Untriaged → Debugger
Product: Firefox → DevTools
Attached image image.png (deleted) —

I can see the content.js file in the Toolbox (see the attached screenshot)

But, I can't see the other files coming from the extension.
(e.g. background.js)

Jason, are those supposed to be accessible in the Sources panel?

Honza

Flags: needinfo?(jlaster)
Attached image screenshot_2019-09-26-15:30:14.png (deleted) —

Background files are supposed to be available in the "background console" (the one you open through about:debugging). Here's a screenshot showing an empty background debugger even though the background script did execute (things are logged in the console).

Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached image image.png (deleted) —

I can still reproduce the problem, my STRs.

  1. Load the attached extension using about:debugging (Load temporary extension)
  2. Click the Inspect button next to the extension entry (in about:debugging)
  3. Check out the (Tab) Toolbox, there are no sources in the Sources tree and there should be at least the content.js source
    (see also the screenshot in comment #2)

You can use the regular Toolbox:

  1. Keep the extension installed
  2. Load google.com
  3. Select the Debugger panel
  4. Expand the reproducer entry in the Sources tree
  5. The content.js file available

BP in the file works as expected.

Chrome also shows just the content.js file since it's the one associated with the current page.

Honza

Flags: needinfo?(jlaster)
Blocks: dbg-addon
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: