Adding a vote and my two cents in this "war".
I used to love FF and use it both at home and at work. After Chrome appeared, I kinda drifted to it for home. I mean, it's light. God knows I've seen enough toolbars and stuff, don't really need them all the time. Agreeing with sparrowhawk, moving to Chrome definitely meant more scrolling if you're checking a lot of tabs and going back and forth much. After a while, it's not so obvious, maybe I got accustomed to it.
Against FF, to this day, I hold the leaking/memory consumption problem. In our work environment almost every day I caught junior SDs waiting minutes for Firefox to load after hot-deploying something. After a couple of hours without closing the browser that is. And at the same time, they were using Chrome for ... a more personal experience with the web
I still recommend FF for work-environments with 1 condition - restart whenever you go on a smoking break
Try stuff that you're sure works on Chrome, debug / polish in Firefox.
And I refuse to comment on IE. I've had it with IE users (as a sort of tech support for a while) so besides basic compliance, now I couldn't care less what works in IE.
Funny story though, for a couple of years, I had the privilege of having a weird IE6 build on one of my work stations that was a test-failer for a lot of different projects (and versions/builds). Our fellow testers were unable to duplicate that particular build for ages. It gave a lot of false negatives (again, weird-hard-to-find-build), but it never missed a beat
Writing things that worked on the first try on that IE was a sort of rite-of-passage for newbies.