Summary: | Web Inspector: Cursor should follow execution line when debugging. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Vsevolod Vlasov <vsevik> | ||||
Component: | Web Inspector (Deprecated) | Assignee: | Vsevolod Vlasov <vsevik> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | apavlov, bweinstein, dubroy, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, yurys | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Vsevolod Vlasov
2012-06-28 09:32:27 PDT
Created attachment 149964 [details]
Patch
Committed r121534: <http://trac.webkit.org/changeset/121534> (In reply to comment #2) > Committed r121534: <http://trac.webkit.org/changeset/121534> Does Eclipse's / Idea's / VS's cursor follow execution line? Not sure we need a shortcut for toggling breakpoint, hence not sure we should change behavior for that. (In reply to comment #3) > (In reply to comment #2) > > Committed r121534: <http://trac.webkit.org/changeset/121534> > > Does Eclipse's / Idea's / VS's cursor follow execution line? Not sure we need a shortcut for toggling breakpoint, hence not sure we should change behavior for that. Sure they do. When debugging recently, I found out that the main reason for me to use mouse in devtools is toggling a breakpoint, it seems very natural to me to have such a shortcut. Often I set breakpoint on some high-level function, then trigger some action on the inspected page and then remove breakpoint and step in until I find low-level function I need and set breakpoint inside it. Almost all of this could be done without touching mouse. Imagine you trigger first breakpoint by running some console command - in this case you don't need to touch mouse at all. I am not insisting on any particular shortcut though. > Often I set breakpoint on some high-level function, then trigger some action on the inspected page and then remove breakpoint and step in until I find low-level function I need and set breakpoint inside it.
> Almost all of this could be done without touching mouse.
> Imagine you trigger first breakpoint by running some console command - in this case you don't need to touch mouse at all.
>
> I am not insisting on any particular shortcut though.
That all sounds reasonable, but I am not sure it is worth a shortcut. Could you answer the question about similar functionality in other IDEs?
(In reply to comment #5) > > Often I set breakpoint on some high-level function, then trigger some action on the inspected page and then remove breakpoint and step in until I find low-level function I need and set breakpoint inside it. > > Almost all of this could be done without touching mouse. > > Imagine you trigger first breakpoint by running some console command - in this case you don't need to touch mouse at all. > > > > I am not insisting on any particular shortcut though. > > That all sounds reasonable, but I am not sure it is worth a shortcut. Could you answer the question about similar functionality in other IDEs? I thought I already did. This functionality is supported by all IDE you mentioned. > > That all sounds reasonable, but I am not sure it is worth a shortcut. Could you answer the question about similar functionality in other IDEs?
>
> I thought I already did. This functionality is supported by all IDE you mentioned.
This looks great then, thank you!
Definitely seems reasonable to me. VS and Eclipse behave this way, and staying consistent with them seems like a good idea. |