Closed
Bug 1070869
Opened 10 years ago
Closed 5 years ago
Debugger object no longer available in a chrome scratchpad
Categories
(DevTools Graveyard :: Scratchpad, defect, P3)
DevTools Graveyard
Scratchpad
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Unfocused, Unassigned)
Details
Bug 749316 added the Debugger object to chrome scratchpads. This no longer seems to work.
|
||
Comment 1•10 years ago
|
||
This was a side-effect of making the scratchpad use the remote debugging protocol: it no longer has direct access to the sandbox the evaluation takes place in. Can you say more about your use case to gauge the importance of supporting it?
|
Reporter | |
Comment 2•10 years ago
|
||
There isn't a strong reason to have it there, IMO. It's convenient when building some tools, but the alternative is a 2-liner.
However, scratchpad.js does still have the original code - it's just broken and doesn't do anything.
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
Scratchpad was removed in Bug 1519103 (Firefox 72). You can check the alternative in https://wiki.developer.mozilla.org/en-US/docs/Tools/Deprecated_tools#Scratchpad .
The Scratchpad bug list was reviewed and I think this bug can be safely closed.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
|
|
||
Updated•5 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•