UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
this is a feature request.

When debugging javascript code, it's very common to want to step into a closure, for example, with jQuery:

    $("#foo").each(function () {
       doSomething();
    });

there are two ways of stepping into the closure here:
1) step into $(), step out, step into each() and step through jQuery searching for the .apply() call... a mess.
2) or, set a breakpoint on the 'doSomething()' line, continue, clear the breakpoint.

this 2nd scenario is "Run to Cursor", visual c++ has had it since v2.0, and edge's f12 tools has it. (they use ctrl-f10 as the keyboard shortcut)

the action is simple:
- attempt to set a (temporary, invisible) breakpoint at the cusor. fail if a breakpoint cannot be set.
- continue execution.
- when execution stops (for any reason), remove the temporary breakpoint.

additionally, it might also make sense to add 'step over or stop at cursor'. which would execute a step over with an additional temporary breakpoint set at the cursor location.

What is the expected behavior?

What went wrong?
?

Did this work before? N/A 

Chrome version: 58.0.3029.81  Channel: stable
OS Version: 10.0
Flash Version: