Bug 143902 - Stepping in the debugger doesn't always advance as one expects - step-over should complete the line
Summary: Stepping in the debugger doesn't always advance as one expects - step-over sh...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Joseph Pecoraro
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-04-17 16:20 PDT by Dean Jackson
Modified: 2017-02-11 01:13 PST (History)
6 users (show)

See Also:

Attachments
Test case (344 bytes, text/html)
2015-04-17 16:20 PDT, Dean Jackson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Jackson 2015-04-17 16:20:56 PDT 
Created attachment 251066 [details]
Test case

For single line statements, calling step in the JS debugger doesn't always advance to the next line.

See the attached testcase.
Comment 1 Radar WebKit Bug Importer 2015-04-17 16:21:27 PDT 
<rdar://problem/20595484>
Comment 2 Joseph Pecoraro 2016-09-28 13:42:13 PDT 
I'll use this bug to track making "step-over" do line based stepping instead of ~statement stepping.

In general, stepping should be significantly improved soon so that you will know exactly what is executing each step. There has been discussion on how step-over should behave in such cases, and it seems "skip all things on this line" is what developers are familiar with.
Comment 3 BJ Burg 2017-02-10 20:22:42 PST 
Joe, is there any reason to keep this bug open any more?
Comment 4 Joseph Pecoraro 2017-02-11 01:13:56 PST 
Yes. The idea of "step-over" being line-based is still valid. Currently we can pause on multiple statements within a line. Moving to line-based (by sending the backend a start offset and end offset of the line) would be an enhancement we could add.