Safari 6 web inspector woes

Eureka! I missed the part where you had to manually opt-out from Crap Inspector. Thanks!

They appear to have tried to give us the webkit version as an option and... failed. How can that happen? I am mostly just suprised that this got released. This and the podcast app have been suprisingly crappy. I hope this is not a sign that loosing the accountability to Steve Jobs has made them lazy.

Safari 6.0 makes my tasks longer and less efficient. Apple you failed. I'm about to jump ship to Chrome. Half my pages stop loading, if I empty the cache and try to reload Safari quits and the Inspector is completely jacked and if I have to continue to rollover the tinest arrow to see what line a piece of CSS is on, I'm going to scream. Thanks alot.

I am using the nightly build of the webkit browser, and I can use the webkit inspector now, or the flawed apple one. However the ability to set breakpoints in inline javascript seems to be broken there as well. You may want to try it, and see if it works for you:

http://nightly.webkit.org

Thank you for this RolandKeijzer unfortionately i can't seem to give you points for helping me. Installing the WebKit and opting to 'Use WebKit Inspector' has provided me a set of working developer tools

By the way, I am blind. The new webkit inspector has a tiny triangle in the top left of the sources tab which allows you to browse the resources and add a debugging tab. Then setting breakpoints works just like it used to. I am back in business.

Hmm.. tiny triangles — they must be part of a new Apple design strategy, less simple more illusive.

Just have to post again and say:

Oh, the humanity, the new inspector is horrible! Argh!

I'm surfing using WebKit Nightly, but webkit html editors like Espresso use the built-in webkit, which has the Safari 6 inspector.

I think I've sent feedback twice to Apple begging to change it back 😐

If anyone here has used XCode to develop ios and mac application you will understand what Apple is trying to do with Safari 6 develop. So far it's failing. Chrome is so much more intuitive.

Thank you Google for Chrome! Bye bye Safari! It's been a great ride but you suck now!

figured out how to set break points in inline scripts (at long last, and after lots of clicking on random interface elements). From the resources tab, with the main document selected, you should have a cookie trail bar across the top of the code view. after the document, there is a green icon that says "DOM Tree". If you click on this icon and switch it to "Source Code" it puts line numbers infront of everything and now you can set break points in the page to your hearts content!!!!

Thank you, BrawnyMan. You answered the original question -- how to set breakpoints on inline code -- before the thread devolved into complaints and Chrome and WebKit nightly.

For everyone else wondering why Apple did what they did to the debugger, someone else mentioned it: they're aligning it with XCode. Change is hard, but where they're going makes sense.

Just wanted to chime in here and say I'm really disappointed with the new web inspector. I love using Safari as my go to browser, but for development, I'm going to have to stick with a combination of Firefox and Chrome. Firebug is still superior to many of the other tools out there and chrome is compatible with codekit, so auto-refresh is a beautiful thing.

unfortunately Apple is chasing after the iphone cashcow and suing samsung. it doesn't care about Safari or much of the accessory software anymore. Thank goodness for Google.