Safari 6: Webkit Web Inspector doesn't work

Fixed!! 🙂

In the file menu, dlick "Develop" and uncheck "Use WebKit Web Inspector"

That is not a fix!

The webkit web inspector is completely broken for me, while the new web inspector is a real pain to use. I feel like it cut my productivity in half. For now I guess I have to move to chrome.

I really dislike the new web inspector. I submitted feedback here asking the at least give us the old one back as an option: http://www.apple.com/feedback/safari.html

I noticed the exact same thing. I think it's a bug for sure. If anyone has found a workaround please share. The other issue I am having is using the new web inspector in investigate the DOM tree. I use the "Inspect Element" option frequently in debugging sites, but now the view seems to have word wrapping on the inspector window which makes reading the code almost impossible if you are inspecting an element that is several level deep in on the DOM. Does anyone know if word wrap can be turned off in this view?

I know you can click on the DOM Tree element and switch to 'Source Code' but them you lose the Element Inspector view.

Just install Nightly build of web kit. And "Use WebKit Web Inspector" will be on place

http://nightly.webkit.org

Install of Nightly build worked for me.

I installed the nightly webkit build and was able to use the webkit inspector, but I can't figure out how to get files open in new scripts tab unless I happen to hit an exception or something. Clicking on line numbers in the Resources tab no longer sets a breakpoint. How do you set a breakpoint now?

Agreed 1000%. Some may say that it's just a matter of getting used to the new inspector UI. However, after having used it constantly for several weeks, I can definitively say that the new UI really is, plainly and simply, bad. It's bad for productivity as far as finding what you need. And it's slower by a large margin when viewing page source info, et al. I can no longer easily find out where a particular CSS property was set. I can no longer disable or override a particular CSS property. The console log isn't always consistent: sometimes it defaults to showing me past logs when I just want to see the current log. The network request timeline is not as useful (I want to see cumulative load time for each resource). The "Issues" section confounds me; I have no idea how to use it so it just gets in the way and makes me think that the developer tools are half-baked. "View Source" no longer shows the raw HTML source but rather Safari's syntax-highlighted version. Often I really do just want to see the raw source. And it's been a pain in the butt trying to memorize what each icon means (this is called "mystery meat navigation" where you see only icons without supplemental text). The only thing I'm happy to see is the new console log history. Everything else is an absolute horror to work with. Did Apple create this new Inspector primarily to help its own, internal developers while not thinking about the majority? For me, the new implementation is nearly useless to work with; I'm probably going to start using Chrome exclusively for web development.

frevh56tyrn wrote:

Agreed 1000%. Some may say that it's just a matter of getting used to the new inspector UI. However, after having used it constantly for several weeks, I can definitively say that the new UI really is, plainly and simply, bad. It's bad for productivity as far as finding what you need. And it's slower by a large margin when viewing page source info, et al. I can no longer easily find out where a particular CSS property was set. I can no longer disable or override a particular CSS property. The console log isn't always consistent: sometimes it defaults to showing me past logs when I just want to see the current log. The network request timeline is not as useful (I want to see cumulative load time for each resource). The "Issues" section confounds me; I have no idea how to use it so it just gets in the way and makes me think that the developer tools are half-baked. "View Source" no longer shows the raw HTML source but rather Safari's syntax-highlighted version. Often I really do just want to see the raw source. And it's been a pain in the butt trying to memorize what each icon means (this is called "mystery meat navigation" where you see only icons without supplemental text). The only thing I'm happy to see is the new console log history. Everything else is an absolute horror to work with. Did Apple create this new Inspector primarily to help its own, internal developers while not thinking about the majority? For me, the new implementation is nearly useless to work with; I'm probably going to start using Chrome exclusively for web development.

Apple, if you're listening, this is the sound of your developers fleeing the platform. This is not hyperbole, this is reality -- Safari is no longer useful to develop for the open-standard web that you've pushed so very hard for.

Agreed as well. I had recently moved to Safari from Chrome and was really appreciating the polish it brought to everything, but a non-functional web inspector is a non-starter for a web developer like myself.

I gave it an honest effort, also for about a week, but found it made 100% of tasks 1000% slower and more difficult. Just having it open effectively broke any web page with heavy JS use.

I sent Apple feedback with a full list of problems from my perspective. I'd encourage others to do the same.

Such a shame... Chrome feels primitive in so many areas of UI integration.

I give up. Safari's web inspector is worthless for examining network requests. I've been using Safari, Chrome and FF, with Safari as my main browser, but no more bcause I cannot do the work I need to.