Is there any particular functionality you're missing? Chrome Dev Tools are really comparable in my opinion. I would like a way to tamper data sent in POST, but I don't think even Firebug has that built in.
It's those minor but intuitive things that we get used to when using firebug. For example:
1) The inspect tool is at the bottom on chrome dev tools. It would have been much more intuitive to keep it at the top of the bar.
2) You don't see a change of cursor when hovering over editable properties. People who never used firebug might have gotten used to this but for me it feels clunky.
3) No single click edit. On firebug you can start editing a property with a single click. Not so on chrome. This is even worse when editing styles. When single clicking a style you don't even see a visual indication that something happened... again feels clunky..
4)Too many tabs that are not bunched according to how often they are used.. I don't think people use Resources, Timeline, Profiles, Audits as often as they use the other tabs.
5) The information is presented in more readable way. When a break point is hit, chrome displays a bunch of tabs on right which are vertical (often empty - because they aren't relevant to this break point) and wasting precious vertical space..
6) Clutter, clutter and more clutter.. just too many sub windows cramped into one another affecting readability...
I know that most of these reasons are subjective and vary across developers but wanted make a list of my own reasons as I found my self trying to use chrome dev tools and always jumping back to firebug.
The tiny little detail that drives me nuts is that, in Chrome, to disable a CSS rule, the checkbox is on the right side of the rule, not the left.
The problem is that I can't visually tell which checkboxes match which rules, because they're too far away. Even worse, the checkboxes only show up on hover, and disappear when you hover just one pixel to the right of them, because the hover area is set wrong. (At least on OSX.)
It's just all the little details the Firebug gets right, and Chrome doesn't seem to, but day after day, they add up.
Yes, this is pretty much it. I think it's more a habits thing than anything and I will have to force myself (at some point) to jump ship completely unless I see some improvement from FF. I understand Firebug, I just need to be able to fully map those onto Chrome, so need to spend a few hours re-learning.
Only other thing I need/want is the FireQuery plugin to help with any jQuery development.
Thanks for the post. Glad to hear Chrome is coming with a few fixes for those annoyances according to your respondents.
I can only comment on 4), in that I use both Resources and Audits frequently. Resources more-so, I'm always clearing site-specific cookies/sessions. Audits is useful when trying to improve site speed, it has a lot of good advice.
