Live data from Hacker News

Things I didn’t know about the WebKit inspector

blog.joocode.com

11–20 of 54 posts

Re: Things I didn’t know about the WebKit inspector

#11

I love tip articles! Here are some more that I use heavily (note that some of these might be Google Chrome only at the moment) The gear in the bottom right of the Chrome inspector has a lot of useful options, such as emulating touch events and preserving the console log upon navigation. The Watch Expressions persist across tabs and I keep "this" as the top watch expression all the time. It makes for an easy quick che…

'this' in the watch expressions and the element id trick are handy!

Re: Things I didn’t know about the WebKit inspector

#12
post #6

Command-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

Re: Things I didn’t know about the WebKit inspector

#13
>> 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

Re: Things I didn’t know about the WebKit inspector

#15
post #13

>> 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

Agree, that could be definitely improved!

Re: Things I didn’t know about the WebKit inspector

#16
I've always felt that firebug has been a little bit better than the chrome developer tools. Now I might reconsider and start using chrome for development instead. The ability to add new css rules in the element view something I've been dreaming about for a long time. The ability to write more than one line of javascript without enabling a different mode is also absolutely fantastic.

Is there a similar list for firebug? A strong advantage of firebug is of course that it's has a bunch of nifty extensions. Which one do you prefer?

Re: Things I didn’t know about the WebKit inspector

#17
very useful, but i really wish Chrome allowed you to replay a HTTP request from the network tab. I just want to right click on e.g a POST request, and send it off to the server again. Whenever i need to do this at the moment i have to switch to LiveHttpHeaders in firefox, which is a pain.

Re: Things I didn’t know about the WebKit inspector

#18

Speaking of web inspectors, did anyone else notice what a tremendous broken piece of crap the one in the latest version of Safari is? It's downright scandalous! I had to manually roll back Safari to 5.1.7 to get the old one back. I will give Apple credit for keeping me hooked on Safari since they're bookmark and history sync across all their devices via the cloud is top notch.

I gave it a cursory glance but haven't had much cause to really use it yet (though I did get some good use out of the console keeping a history of log files). What kind of issues have you been having?

Re: Things I didn’t know about the WebKit inspector

#19
post #17

very useful, but i really wish Chrome allowed you to replay a HTTP request from the network tab. I just want to right click on e.g a POST request, and send it off to the server again. Whenever i need to do this at the moment i have to switch to LiveHttpHeaders in firefox, which is a pain.

Charles (www.charlesproxy.com) makes this kind of thing pretty easy. Well worth the money, in my book.
Post reply on HN