| Summary: | Stepping in the debugger doesn't always advance as one expects - step-over should complete the line | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Dean Jackson <dino> | ||||
| Component: | Web Inspector | Assignee: | Joseph Pecoraro <joepeck> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | bburg, graouts, inspector-bugzilla-changes, joepeck, jonowells, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
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. Joe, is there any reason to keep this bug open any more? 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. |
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.