- Tools like YSlow and PageSpeed require Firebug.
- You can't disable the browser cache from FF devtools, which really sucks when you are trying to debug a broken redirect.
- When inspecting an element in FF devtools, :before and :after CSS properties will not be shown. I wasted many hours debugging a CSS refactor because of this (imagine going up the DOM, comparing computed CSS properties until you reach the root). Both Firebug and Chrome devtools will show :before and :after properties.
I think Firebug and the Chrome devtools are comparable in quality.
It was fixed recently. https://hacks.mozilla.org/2013/09/new-features-in-the-firefo...
And on that, I was plesently surprised to see Chrome will now display :before and :after psuedo elements in the DOM structure
Good luck trying to get a webfont to render the same (or look any good) in Chrome as it does in IE and FF on Winderps. The sheer fact that it isn't IE for once...
The font thing, while somewhat recent in usage, should have been in Chrome ages ago. Not going to bother getting into Chromes other more critical flaws as I feel like these threads devolve into this kind of shit too easily.
Just sucks that Chrome has gone from this cool browser that actually is progressive, to some kind of Ad-friendly extension of Google that just qualifies as "better than IE!".
Methinks you should jump on FF, it's better, and not because it may not support some arbitrary HTMl5 spec that we wont see for half a decade.