New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 752443 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Precise/column breakpoint marker at for-loop increment substatement missing

Reported by account-...@dlehmann.eu, Aug 4 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/59.0.3071.109 Chrome/59.0.3071.109 Safari/537.36

Steps to reproduce the problem:
1. Open attached example.html
2. Open Developer Tools -> Debugger
3. Set breakpoints in line 8 and 14 (the for loops)
4. Reload

What is the expected behavior?
- the for loops only differ in the declaration of the loop variable (one with let, other with var)
- precise/column/inline breakpoint markers should appear in the same way for both loops
- in particular, there should be a inline breakpoint marker at the i++ increment statement in both loops

What went wrong?
- the first loop (where the loop variable is declared with let) gives us an inline breakpoint marker at i++ (correct!)
- the second does not (wrong).
- why is there a difference between let and var-declared loop variables?

Did this work before? N/A 

Chrome version: 59.0.3071.109  Channel: dev
OS Version: Ubuntu 16.04. 64bit
Flash Version: 

see also the attached screencapture for demonstration
 
example.html
506 bytes View Download
screencapture.ogv
515 KB View Download
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Status: Fixed (was: Assigned)
This one should be fixed in M61 and I verified that it's fixed in ToT.

Sign in to add a comment