Last Comment Bug 696830 - Add a "Closure" scope to the debugger property view
: Add a "Closure" scope to the debugger property view
Product: Firefox
Classification: Client Software
Component: Developer Tools (show other bugs)
: unspecified
: x86 All
-- normal (vote)
: ---
Assigned To: Victor Porof [:vporof][:vp]
: J. Ryan Stinnett [:jryans] (use ni?)
Depends on:
  Show dependency treegraph
Reported: 2011-10-24 12:09 PDT by Victor Porof [:vporof][:vp]
Modified: 2011-10-27 01:15 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

v1 - added scope + fixed tests (5.13 KB, patch)
2011-10-24 12:09 PDT, Victor Porof [:vporof][:vp]
dcamp: review+
Details | Diff | Splinter Review

Description User image Victor Porof [:vporof][:vp] 2011-10-24 12:09:57 PDT
Created attachment 569131 [details] [diff] [review]
v1 - added scope + fixed tests

Per a discussion in bug 676592, the property view may need a "Closure" scope.

"Apparently WebKit also displays a "Closure" scope in some cases. For example, when the execution pauses at the first debugger statement in:

This is in the eval code. I'm not sure whether it's more helpful than putting it in the local scope, nor if our engine will expose that bit of information."

Note You need to log in before you can comment on or make changes to this bug.