When debugging a statement like this: -- snip -- task.story().isCollapsed() -- snap -- it is quite hard to step into the second function call (isCollapsed()) with webkit. This is not exactly easy with other debuggers too, but what most of them do (gdb most importantly) is if you use step into on that statement you get into story(), and if you step out from that you get back to the original statement - but before isCollapsed() is called. Webkit sadly doesn't behave this way - but it should (thats the bug report). One workaround which works sometimes is to to step into story and then step to the last statement therein - then step over that twice, which lets the focus remain in that method, and then press step into again. That at least gets you into the second method - however very clumsily. (Which could be argued is a second bug actually) So please improve the way the debugger works so that step out only steps out of the current function and not also of all subsequent calls on the return value from that function. Regards, Martin
The script debug tools have improved quite a bit since 2009. @Martin what's the status here, have your needs been fulfilled?
Works for me