Remember, there isn't any kind of really legitimate API for 100% determining which browser you're running in. There's a lot of ad-hoc methods which usually work.
These folks spent extra effort to block it from even TRYING to run in FireFox.
How are the FireFox devs supposed to see the bad performance that they need to fix for Inbox to work right if they can't run it at all?
Also, with respect to performance, this comment in the article might shed some light:
"Also see Bugzilla entry. The use of spare arrays with huge indexes was a performance issue in Firefox. It's been fixed in Inbox and in FF but not shipped in FF yet. (https://bugzilla.mozilla.org/show_bug.cgi?id=1087963)"
When you get bug reports from internal customers it's never "the site isn't working in Firefox 33 with all extensions turned off. It loads but is a little slow.". The bug report you get is simply "it isn't working, you get a blank page".
Answering those types of emails cost real money.
What cost is there?
If I've switched UA string Google might not even be able to tell, without actively seeking out the information, that other browsers are using it - how then could that be an extra cost?
School me, please.