CTRL+SHIFT+F searches through all the scripts. I use this primarily to navigate through code i.e CTRL+SHIFT+F "function showDialog("
I think I prefer Command+Shift+O that the article suggests in this case.
Things I didn’t know about the WebKit inspector
41–50 of 54 posts
Re: Things I didn’t know about the WebKit inspector
#42Write "debugger" in your source code, chrome will drop you into debugging mode when that line is read. The console will be in context of your "debugger" statement.
Re: Things I didn’t know about the WebKit inspector
#43Earlier quoted context omitted.
Thanks, but the chrome on my iPhone/iPad leaves something to be desired
Compared to Safari? Really? I'm honestly surprised, as an iPhone user who had to put up with Safari for 3 years. The only nice feature about it is the Readability-powered Reader button.
Safari is the only browser on iOS with JIT enabled.
Re: Things I didn’t know about the WebKit inspector
#44Command-K also clears the console, just like it does in terminal. Awesome stuff. Unfortunately the `x = _` trick to save the output of the last command to variable x does not work, but that would be really awesome if they put that in!
`$_` is coming to WebKit soon: https://bugs.webkit.org/show_bug.cgi?id=93377
Already in Canary!
Re: Things I didn’t know about the WebKit inspector
#45>> Console, write more-than-1-line commands: shift-enter does the trick. Pressing enter at the end of the script runs it. You need to shift-enter every line, not as usable as Firefox/Firebug. Also tab is still not working. This is the reason why I am still using Firefox for development purpose. http://code.google.com/p/chromium/issues/detail?id=35487
The upcoming Snippets functionality has a great story for this. You can turn it on in devtools experiments, but it's likely gonna get revised a bit before it ships.
Re: Things I didn’t know about the WebKit inspector
#46>> Console, write more-than-1-line commands: shift-enter does the trick. Pressing enter at the end of the script runs it. You need to shift-enter every line, not as usable as Firefox/Firebug. Also tab is still not working. This is the reason why I am still using Firefox for development purpose. http://code.google.com/p/chromium/issues/detail?id=35487
The upcoming Snippets functionality has a great story for this. You can turn it on in devtools experiments, but it's likely gonna get revised a bit before it ships.
Hi Paul, thanks for your information and I will definitely check it out when it is ready.
Re: Things I didn’t know about the WebKit inspector
#47Earlier quoted context omitted.
Compared to Safari? Really? I'm honestly surprised, as an iPhone user who had to put up with Safari for 3 years. The only nice feature about it is the Readability-powered Reader button.
Safari is the only browser on iOS with JIT enabled.
Doesn't excuse its irritatingly outdated UI.
Re: Things I didn’t know about the WebKit inspector
#48In Chrome when viewing a js file the "{ }" button (pretty print) in the lower left will un-minify the file. Most useful for debugging live sites.
Re: Things I didn’t know about the WebKit inspector
#49Earlier quoted context omitted.
Compared to Safari? Really? I'm honestly surprised, as an iPhone user who had to put up with Safari for 3 years. The only nice feature about it is the Readability-powered Reader button.
Safari is the only browser on iOS with JIT enabled.
not if you jailbreak :P
search for "nitrous" on cydia
Re: Things I didn’t know about the WebKit inspector
#50CTRL+SHIFT+F searches through all the scripts. I use this primarily to navigate through code i.e CTRL+SHIFT+F "function showDialog("
I think I prefer Command+Shift+O that the article suggests in this case.
the difference is that CTRL+SHIFT+F works from every tab in the chrome inspector and searches globally i often just copy paste the line i want to debug from my editor in there be it a function or declaration within a function.