Confirmed users
497
edits
Debugger: Difference between revisions
Jump to navigation
Jump to search
→Accessor Properties of the Debugger.Frame Prototype Object: Note that onStep and onPop are ignored on frames that aren't running JavaScript.
(→Accessor Properties of the Debugger.Frame Prototype Object: Clarify behavior when there are several Debugger.Frame instances with onPop handlers for a given frame.) |
(→Accessor Properties of the Debugger.Frame Prototype Object: Note that onStep and onPop are ignored on frames that aren't running JavaScript.) |
||
| Line 323: | Line 323: | ||
What constitutes "a small amount of progress" varies depending on the implementation, but it is fine-grained enough to implement useful "step" and "next" behavior. | What constitutes "a small amount of progress" varies depending on the implementation, but it is fine-grained enough to implement useful "step" and "next" behavior. | ||
This property is ignored on frames that are not executing JavaScript code, like <code>"call"</code> frames for calls to host functions and <code>"debugger"</code> frames. | |||
<dt>onPop | <dt>onPop | ||
| Line 336: | Line 338: | ||
When a generator frame yields a value, SpiderMonkey calls its <code>Debugger.Frame</code> instance's <code>onPop</code> handler, if present, passing a <code>yield</code> resumption value; however, the <code>Debugger.Frame</code> instance remains live. | When a generator frame yields a value, SpiderMonkey calls its <code>Debugger.Frame</code> instance's <code>onPop</code> handler, if present, passing a <code>yield</code> resumption value; however, the <code>Debugger.Frame</code> instance remains live. | ||
This property is ignored on frames that are not executing JavaScript code, like <code>"call"</code> frames for calls to host functions and <code>"debugger"</code> frames. | |||
<dt>onResume(<i>value</i>) | <dt>onResume(<i>value</i>) | ||