Hacker News Reader

For my dislike of it? No, it's that I love firebug's way of displaying your CSS entries, and the webkit inspectors way is just less enjoyable to me. I like that in Firebug you inspect your CSS like you would normal CSS, but in inspector it's presented differently. It also has a lot of quirks (try changing a color, it will bork on whitespace in a strange way).

View on HN

I see this complaint leveraged at the web inspector a lot, but I don't really understand it. It seems like the differences are very subtle.

http://i.imgur.com/amWMy.png vs. http://i.imgur.com/ysH0a.png

(As an aside, note that FireBug doesn't know that the font color has been overridden by the font tag.)

I'm curious what changes specifically you would make to improve it?

The difference is that the rules are rendered using actual CSS syntax, rather than the section heading control.

This makes it very easy to scan because as a web developer, your brain is already trained to parse CSS syntax easily.

The controls in the webkit UI may seem richer, but they aren't actually as efficient as the simple code view that Firebug uses.

It wouldn't seem like a big deal, but in practice I've found I greatly prefer firebug's display.

Reply on news.ycombinator.com