Open
Bug 1542574
Opened 5 years ago
Updated 2 years ago
[jsdbg2] findAllGlobals / onNewGlobalObject do not belong on Debugger
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: jimb, Unassigned)
References
(Blocks 1 open bug)
Details
The Debugger.prototype.findAllGlobals method and the Debugger.prototype.onNewGlobalObject debugger hook don't actually use any information provided by the Debugger. They are also unusual among Debugger hooks in that they observe the entire runtime, not just a given set of debuggees, which is ugly. Both of these could be replaced by an XPCOM or chrome WebIDL interface, and removed from the Debugger API.
|
Reporter | |
Updated•5 years ago
|
Summary: [jsdbg2] findAllglobals / onNewGlobalObject do not belong on Debugger → [jsdbg2] findAllGlobals / onNewGlobalObject do not belong on Debugger
|
||
Updated•5 years ago
|
Priority: -- → P3
|
||
Updated•4 years ago
|
Blocks: js-debugger
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•