Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Can't debug scratchpad scripts in the browser debugger




Developer Tools: Debugger
5 years ago
2 years ago


(Reporter: rc, Unassigned)


(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [chrome-debug])



5 years ago
Run a script from a scratchpad in a Browser Context, ideally something that will stick around in a timer or similar.

Open a Browser Debugger and search for Scratchpad.

The script will appear in the Debugger list (probably as Scratchpad/1 or 2) but selecting it will only display "Loading..." in the Source area.

Comment 1

5 years ago
for bonus points, making scratchpad scripts show up in the content debugger would be to.
Seems like a dupe of bug 813087, but you focus on the script we pass to eval, which is a more general problem. I don't think we have a solution until bug 637572 is fixed.

Comment 3

5 years ago
similar but different. This is mostly about the script showing up in the list but not being accessible. I agree that bug 637572 would fix it.
Depends on: 637572

Comment 4

5 years ago
filter on BLACKEAGLE.
Priority: -- → P3
Whiteboard: [chrome-debug]
Duplicate of this bug: 903214
Depends on: 905700
No longer depends on: 637572


3 years ago
Blocks: 1070868


3 years ago
Summary: Unable to debug Scratchpad scripts in the Browser Debugger → Can't debug scratchpad scripts in the browser debugger
Duplicate of this bug: 1109223

Comment 7

2 years ago
any news on this bug ?
(In reply to inscription from comment #7)
> any news on this bug ?

I'm really sorry, but this bug is currently not on anyone's radar :-(

I'd love to look into it myself, but am too busy with service worker debugging at the moment.
You need to log in before you can comment on or make changes to this bug.