Things I didn’t know about the WebKit inspector • Hacker News Board

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

#51

Post by SquareWheel » Sat, Aug 11, 2012, 12:03 PM UTC

euroclydon wrote: post #43

mitjak wrote: post #40

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

If Jailbroken and you have 99 cents, you can install Nitrous in Cydia to get nitro everywhere. It gave me 3.5x faster performance on Sunspider.

But even if not, how many mobile websites use heavy JS? Chrome appears to use page pre-fetching as well, or at least that's what I gather from the "preload webpages" setting.

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

#52

Post by [deleted] » Sat, Aug 11, 2012, 3:27 PM UTC

btipling wrote: post #14

tterrace wrote: post #4

"Break on DOM modification" is going to be a big time saver for when an ajax call fetches a bit of html with a in it.

Don't do this.

[deleted]

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

#53

Post by Stratoscope » Sat, Aug 11, 2012, 7:54 PM UTC

Here's one I stumbled into the other day: You can inspect the inspector!

This is in Chrome for Windows (haven't tried Safari or Chrome for Mac).

Hit F12 to open the inspector.

If it is docked, click the undock icon so it's in a separate window.

Make sure the focus is on the separate inspector window (click its titlebar to be sure), and hit F12 again. This opens another inspector window where you can inspect the first one.

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

#54

Post by datbates » Thu, Aug 16, 2012, 6:47 PM UTC

boonedocks wrote: post #5

Can anyone point to a guide for using the web inspector in Safari 6? It looks like it could be powerful, but it is not as user-friendly as the Safari 5 and Chrome inspectors. It feels like a step back.

Has anyone figured out how to set a breakpoint in the actual page (not a .js file)? There are no line numbers in the inspector to click on. I complained to Apple. I also can't figure out how to add script files to the sources tab in the new webkit version of the inspector. Also clicking on the line numbers in the resources tab of the new webkit inspector no longer sets a breakpoint. I've had to go back to 5.x since I can't set breakpoints where I need to... Ideas?