I've used the two extensively, and the only thing (for my use case) that Chrome has over FF is interface speed. Here are a few things FF does really well over Chrome.
Low level extension access to the browser: This is the reason you don't have Noscript or HTTPS Everywhere in Chrome, it's also the reason mouse gestures are fundamentally broken on Google's browser. For example perform a gesture to open a new tab, then perform a gesture to close it. Oops, you can't, since extensions are disabled in certain types of pages on Chrome due to its security model.
Search as you type: You actually have to hit CTRL+F in Chrome to start finding stuff, versus just starting to type in FF.
Tab activity notifications: On FF, I can have Gmail, Reader, etc.. pinned as app tabs, and if they get updated with new items the tab gets highlighted. Chrome, for some strange reason doesn't do this and you have to keep opening the tabs to check for updates.
Search keywords: Much more straightforward to add in FF, just click on a search field and select "Add keyword for this search". Chrome automatically adds just about every search engine/form you come across to a huge list, which you then have to trawl in order to customize the one you want.
Bookmarks & History: Chrome's bookmark manager sucks big time, I guess Google wants you to search and not bookmark. FF has a half decent manager with tag support. The Wonderbar also works a lot better than the Omnibar when searching your history and bookmarks.
Tiddlywiki: This is the big one for me (although only tangentially Chrome's fault), I use tiddlywiki extensively and FF is the only working browser on non-Windows platforms.
So all of these annoyances in Chrome negate the gain I get from its speed by a large margin. Again, this is my particular use case, but I definitely get stuff done quicker in FF than in Chrome.
And by the way, the initial extension breakage is fixed on FF 7.0.1, which was just released.