Open
Bug 638044
Opened 13 years ago
Updated 1 year ago
JavaScript needs whole-object watchpoints
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: jimb, Unassigned)
References
(Blocks 2 open bugs)
Details
It would be neat to have watchpoints that watch all properties on a particular object, watchpoints on property additions, deletions, reconfigurations, and so on.
Comment 1•13 years ago
|
||
See also Andreas Gal's comment on See also https://bugzilla.mozilla.org/show_bug.cgi?id=579342 The 'recursion' problem, or the extension of watchpoint to variables is critical: var foo ={}; foo.bar ="baz"; We need to know both that foo.bar was created *and* that foo was created. If the developer is concerned with 'foo' they don't want to have two different approaches if 'foo' is a property or a variable.
Assignee | ||
Updated•13 years ago
|
Component: JavaScript Debugging/Profiling APIs → JavaScript Engine
Comment 2•11 years ago
|
||
As bug 637913 indicates this issue is having a high priority for Firebug. Our use case is to stop the script execution on property addition and removal[1]. Sebastian [1] http://code.google.com/p/fbug/issues/detail?id=4162
Comment 3•11 years ago
|
||
I believe implementing Object.observe (bug 800355) would work here.
Depends on: 800355
Comment 4•11 years ago
|
||
So maybe this bug should be merged into bug 800355? Or do "watchpoints" cover something additional or different? Sebastian
Reporter | ||
Comment 5•11 years ago
|
||
Perhaps not additional, but different. Object.observe reports activity on some subsequent event loop tick, whereas debugger watchpoints need to trigger immediately when the modification takes place.
Comment 6•11 years ago
|
||
I'm not quite sure what you mean with "some subsequent event loop tick" but it sounds like we really need watchpoints as you describe them for our use case. Sebastian
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•