New issue
Advanced search Search tips

Issue 784852 link

Starred by 1 user

Issue metadata

Status: Fixed
Closed: Nov 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Sign in to add a comment

Breakpoint jumps over function declaration

Reported by, Nov 14 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 DevTools > Sources > select example.html
3. Reload
4. Set breakpoint in line 7 (buggy case)
5. Set breakpoint in line 11 (correct case)

What is the expected behavior?
- Breakpoint in line 7 (step 4.) should slide to the same location as the breakpoint in line 11 (step 5.), namely the function body that is following.

What went wrong?
- Breakpoint in line 7 "jumps over" function, that is, it is slided to line 16 (variable declaration) instead of line 13.
- Unclear why breakpoint in line 7 should behave differently from line 11 (both comment lines, both are followed by a function declaration).

Did this work before? N/A 

Chrome version: 59.0.3071.109  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: 

- See also attached screencapture for video demonstration of bug.
468 bytes View Download
1.0 MB View Download

Comment 1 by, Nov 14 2017

Status: Assigned (was: Unconfirmed)
Thanks for the report.  Based on the video, it looks like the last click performed is clicking on Line 9, and the breakpoint gets added to foo().. strange.  kozy@, could you please take a look?
That's right, I basically wanted to find out "from which line on" the breakpoint is added to the function body (the correct behavior). Apparently line 9, 10, and 11 work as expected (the breakpoint is set in the function), but earlier lines 6, 7, and 8 are having the problem (the breakpoint is set at the variable declaration after the function).

Comment 4 by, Nov 30 2017

Status: Fixed (was: Assigned)

Sign in to add a comment