One of the problems with Firefox is that it doesn't read older HTML code very well and hence, has been causing huge problems for the server. This is a result of lazy coding, a fault that seems rampant these days. My daughter is actually in her final set of modules for her Web Design and Advanced Programming course, and she sees the problems a lot.
Google's Chrome browser however, it pretty basic, is backward and frontward compatible, is small, clean code and performs much like the former best browser on the net a number of years ago, before that

AOL bought it. Netscape was at it's pinnacle with 4.74 and was set to dominate the browser markets, until AOL ruined it with 5.0. AOL is kind of redundant.. why would anyone pay a secondary ISP to access the net after they have already accessed via Verizon, RR or up here say Rogers or Shaw? Makes no sense to me.. but what do I know.
FireFox is a pretty stable browser, it is based on open source code, so lots of nice apps available, however, compliancy across the board is lacking. And they say IE has issues.. both the 2 major browsers could learn a lot from Google's Chrome.
With the new server format, Kris is trying to make sure that is will be cross-platform compliant for all browsers, like Safari, Opera, Chrome, FireFox, IE as well as whatever NetScape is these days.
I do like the fact that there are addins for Firefox to view IE based or compliant apps in it's native environment. That is useful and a desireable feature to have in any browser.