Comments on: Chrome: a silver lining for developers

By: Kristof

Kristof — Thu, 18 Aug 2011 06:07:38 +0000

Hey,

This theme was custom made It features … ME!

Thanks for asking,

Kristof

By: Niki Q

Niki Q — Mon, 17 Jan 2011 20:55:52 +0000

Hi what theme are you using on this site? I love it

By: Han Sanosyan

Han Sanosyan — Fri, 03 Dec 2010 18:28:21 +0000

Very informative put up, love the way you write and I think that the data helps in a way. I don’t usually say this, but I feel this can be a nice job done. When you prefer to exchange links, I would be very happy to supply a hyperlink again to your site. Hope to hear from you soon. Cheers

By: Pat

Pat — Wed, 09 Dec 2009 16:10:16 +0000

I find that not having the css link not show you the actual line number that the style is set in the file is a pretty big reason for me continuing to use Firebug. If it wasn’t for that one feature, that I use pretty constantly, I would be 100% Chrome.

By: Sabra

Sabra — Wed, 29 Apr 2009 16:19:11 +0000

I have already switched to Chrome permanently, since this lightweight browser rocks! For development, I was surprised by the built in features. What a bonus for developers! Thanks for breaking it down!

By: Mateo

Mateo — Sun, 04 Jan 2009 05:36:19 +0000

To me, this is not as powerful as Firebug and the addons for Firebug
FF is heavy on resources but imy PC doesn’t have problem to handle too many windows and tabs, so, i can live with it.

By: Kristof

Kristof — Mon, 22 Sep 2008 15:19:33 +0000

Hey Lagaffe,

Thanks for the additional info. I had no idea that the developer tools were actually a part of Webkit. Thanks for setting me straight! I’ll make sure to check those tools in Safari!

By: Lagaffe

Lagaffe — Mon, 22 Sep 2008 14:43:55 +0000

And he did it again :p

The information can also be found on: http://trac.webkit.org/wiki/Web%20Inspector

By: Lagaffe

Lagaffe — Mon, 22 Sep 2008 14:43:16 +0000

Looks like the form filtered the XML code :-s

WebKitDeveloperExtras

By: Lagaffe

Lagaffe — Mon, 22 Sep 2008 14:41:52 +0000

All the developer tools you’re talking about are part of Webkit and are available in Safari as well.

On a mac you need to activate them by excuting “defaults write com.apple.Safari WebKitDeveloperExtras -bool true” in terminal. Activating the internal debug menu is nice as well: “defaults write com.apple.Safari IncludeInternalDebugMenu 1″

On Windows, you’ll have make sure that the following lines are in your preferences file at the location “C:\Documents and Settings\\Application Data\Apple Computer\Safari\WebKitPreferences.plist” (where should be your Windows user name):
WebKitDeveloperExtras