3 ms·
I actually use Chrome Dev tools more than Firebug these days, but that's because I do work on Chrome Extensions. They're typically Google: great on a technical
by nailer 16y ago
I actually use Chrome Dev tools more than Firebug these days, but that's because I do work on Chrome Extensions.
They're typically Google: great on a technical level, with a somewhat sketchy UI.
One tip: to add a new item to a style click the whitespace area to the right of '{ '.
- te_chris 16y agoI was scratching my head trying to work this out the other day - I ended up heading back to FF and Firebug. Thankyou!
- masklinn 16y ago> They're typically Google: great on a technical level, with a somewhat sketchy UI. They come mostly from the Webkit project itself actually. I'm sure Chrome contributes, but the main driver is Webkit (thus probably Apple)
- rahoulb 16y agoJust on an appearance level, the inspector in Safari is significantly better looking than the one in Chrome (although functionally they seem pretty much equivalent)
- masklinn 16y agoThe only significant differences I noticed are that the Safari/Webkit version has nice gradients (in Chrome, the "tools" tab bar is flat and each section gets a "depressed" gradient when selected, in WebKit the whole bar has a gradient giving it "volume", nicer to look at) and the whole bar is draggable in Safari (for resize) whereas in Chrome you have to grab the intersection between the tools and the actual page. The former is a nice detail on Saf's part but not really important, the latter is a real pain in Chrome as I'm mostly using Safari/Webkit for my development.
- wahnfrieden 16y agoI just want to note that if you look at the maintainers list for webkit, it's full of Google employees. I don't know specifically who contributes to the inspector though.