Closed
Bug 1362428
Opened 8 years ago
Closed 8 years ago
variables bound with let/const not shown in Scopes when step out of function
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1432885
People
(Reporter: account-mozilla-bugzilla, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170418123106
Steps to reproduce:
1. Open attached example.html in Firefox 53.0 or Firefox Developer Edition 54.0a2 (both affected, new and old debugger!).
2. Open Developer Tools, go to Debugger.
3. Set breakpoint in line 10 (first line in function).
4. Reload to hit breakpoint.
5. Click "step out".
Actual results:
- "Scopes" in debugger shows function scope with "someVar" variable, not a block scope with "someLet" and "someConst" variables.
- This seems inconsistent since execution after the "step out" pauses before leaving the function (and thus its scope): Why are let/const bound variables no longer visible, but var bound ones are?
Expected results:
- "Scopes" in debugger should also show block scope with "someLet" and "someConst" variables.
- This is also the behavior when setting a breakpoint at the closing brace and hitting that breakpoint (see screen capture video): "someLet", "someConst", and "someVar" are all visible as expected.
| Reporter | ||
Updated•8 years ago
|
Component: Untriaged → Developer Tools: Debugger
Version: 53 Branch → 54 Branch
| Reporter | ||
Comment 1•8 years ago
|
||
| Reporter | ||
Comment 2•8 years ago
|
||
Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=923975 ("Having to step out of a function twice so we can inspect its return value is confusing")
Comment 3•8 years ago
|
||
Yes - i think that's related
I opened an issue on github: https://github.com/devtools-html/debugger.html/issues/3599
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•