Obvious problems goes unnoticed: search results page kept burning cpu if I keet it open in desktop Firefox. (Installed an extension to fix it and haven't tested lately.)
It's hard to belive this can happen without anyone caring at such a big place.
At a company that seems to be attracting the best and brightest it is really hard to belive this isn't intentional.
Then again I've been equally wrong before.
Sounds like, based on the descriptions here, they're doing the latter, right? Infinite scrolling on Chrome vs. paged viewing on Firefox, for instance.
Fix it, just like any other website out there.
Maybe FF just isn't a very good browser? You can be standards-compliant while implementing the standards with performance problems and ugly corner-cases.
This is the same story as when Google made Inbox a "Chrome-Exclusive" that also didn’t run in Safari, Opera, or even fucking Chromium.
It’s just anticompetitiveness.
I find it interesting how a word's proper usage is in a case that it's opposite would work better!
Anticompetitive is the right word in your sentence, of course, but google isn't anti-competitive in this case with firefox. It is ultra-competitive!
Firefox's engine is different and makes many different decisions with regards to implementation detail. Since the web standards rarely constrain things like, say, time to complete a reflow step in mutating a page when a DOM element has its visibility property changed, standards-compliant browsers can make different decisions on these bits of detail that lead to practically very different experiences.
In general, if it works on Chrome it'll probably work on Safari, and it is not guaranteed to work on Firefox, IE, or Edge without further testing.