Live data from Hacker News

Things I didn’t know about the WebKit inspector

blog.joocode.com

31–40 of 54 posts

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

#31

The $0 thing will save me a lot of time. I often spend a while figuring out how to select a specific element with DOM queries, or assign it a special ID and then do the whole document.getElementById malarkey.

Even better: there is a selection history. $1 get you the item you selected before the one that is currently selected, $2 the one before that, etc.

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

#32

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 kind of like it but the console is broken-slow. a simple console.log(foo) doesn't draw anything for a second or two after the event fires and even then it's empty for another moment while the inspector decides what to draw. Very odd.

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

#33
post #18

Earlier quoted context omitted.

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?

Half the features missing, impossible to navigate.

That's actually completely false. Just about all of the features are there, but they have been reorganized a lot. It seems like they're trying to align the organization of their inspector more with the way the debug tools in XCode work, so that the experience is unified across them. It's a bit tough to get used to if your habits are with the old inspector, but it's actually not too bad once you start getting the hang of it. Just a rearchitecting of your brain map.

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

#34

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.

If you log into Chrome, your bookmarks, history, plugins, settings, etc. will sync across all Chromes that you log into with the same user/pass.

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

#36

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.

If you log into Chrome, your bookmarks, history, plugins, settings, etc. will sync across all Chromes that you log into with the same user/pass.

Thanks, but the chrome on my iPhone/iPad leaves something to be desired

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

#37

Earlier quoted context omitted.

Half the features missing, impossible to navigate.

That's actually completely false. Just about all of the features are there, but they have been reorganized a lot. It seems like they're trying to align the organization of their inspector more with the way the debug tools in XCode work, so that the experience is unified across them. It's a bit tough to get used to if your habits are with the old inspector, but it's actually not too bad once you start getting the hang…

[deleted]

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

#38

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…

After reading the article and your comment, I'm encouraged to give Javascript another chance. Your guess at how you would consider Javascript if you didn't use Chrome's developer tools is actually spot on to how I find it... I am a Firebug user and not a fan of Chrome's tools, but if Firebug has these kind of JS capabilities I've yet to discover them. I must confess, I haven't really looked hard enough, and it looks like JS deserves another shot.

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

#39
post #31

The $0 thing will save me a lot of time. I often spend a while figuring out how to select a specific element with DOM queries, or assign it a special ID and then do the whole document.getElementById malarkey.

Even better: there is a selection history. $1 get you the item you selected before the one that is currently selected, $2 the one before that, etc.

Oh man, this is the best link and comment thread all week. Thanks!

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

#40

Earlier quoted context omitted.

If you log into Chrome, your bookmarks, history, plugins, settings, etc. will sync across all Chromes that you log into with the same user/pass.

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.
Post reply on HN