5 ms·

Google’s web products have always worked with Firefox to my knowledge. Maybe they run a bit faster on Chrome but I don’t recall them ever being broken on Firefo

Google’s web products have always worked with Firefox to my knowledge. Maybe they run a bit faster on Chrome but I don’t recall them ever being broken on Firefox. Perhaps I’m wrong. Can you cite incidents of Google’s stuff not working right on Firefox (or Safari even). Also which features enable developers to create sites that don’t work in Firefox and Safari? (I really don’t know. I’m not a web developer.)

tgv 3y ago
I'm a lifelong FF user, and I had problems with google docs in the beginning. I vaguely remember it was using JS features that FF hadn't implemented yet. Currently, Chrome has a number of CSS features that Firefox and/or Safari don't support. You can find them at [1]. Some make life a bit easier, and devs use them because they like easy or even because they think everyone should force their browser maker to adapt all those features ASAP. In an old thread, I explained that my code ignores these features because we want to be compatible with as many users as possible. I got some miffed replies saying we should make our users upgrade. Really. Then there are also APIs in Chrome that have not been standardized, and some of which should not be in a browser (IMO), like USB access (see [2]). Some of that is an attempt by Google to replace "native" applications by web pages, which would give them even more leverage. [1] https://caniuse.com/?compare=chrome+115,firefox+116&compareCats=CSS https://caniuse.com/?compare=chrome+115,firefox+116&compareC... [2] https://caniuse.com/?compare=chrome+115,firefox+116&compareCats=JS%20API https://caniuse.com/?compare=chrome+115,firefox+116&compareC...
acdha 3y ago
Google Meet reported errors for Firefox users which no other service had problems with. Google Cloud’s login page frequently broke for Firefox users. YouTube was famously slower for a long period of time where they used a proprietary API which only Chrome supported instead of the standard API which Firefox and Safari implemented. I suspect that all of those weren’t malice as much as neglect but for such a large company it’s definitely not a lack of resources if they choose not to test on browsers they don’t make. The real damage, however, was not things actually breaking but the constant push to use Chrome. If you used Firefox you would be prompted to do that frequently visiting Google search, mail, YouTube, etc. with various allegations of better performance which didn’t hold up in testing.
khimaros 3y ago
cloud console is unusably slow in Firefox

tgv 3y ago

I'm a lifelong FF user, and I had problems with google docs in the beginning. I vaguely remember it was using JS features that FF hadn't implemented yet. Currently, Chrome has a number of CSS features that Firefox and/or Safari don't support. You can find them at [1]. Some make life a bit easier, and devs use them because they like easy or even because they think everyone should force their browser maker to adapt all those features ASAP. In an old thread, I explained that my code ignores these features because we want to be compatible with as many users as possible. I got some miffed replies saying we should make our users upgrade. Really. Then there are also APIs in Chrome that have not been standardized, and some of which should not be in a browser (IMO), like USB access (see [2]). Some of that is an attempt by Google to replace "native" applications by web pages, which would give them even more leverage. [1] https://caniuse.com/?compare=chrome+115,firefox+116&compareCats=CSS https://caniuse.com/?compare=chrome+115,firefox+116&compareC... [2] https://caniuse.com/?compare=chrome+115,firefox+116&compareCats=JS%20API https://caniuse.com/?compare=chrome+115,firefox+116&compareC...

acdha 3y ago

Google Meet reported errors for Firefox users which no other service had problems with. Google Cloud’s login page frequently broke for Firefox users. YouTube was famously slower for a long period of time where they used a proprietary API which only Chrome supported instead of the standard API which Firefox and Safari implemented. I suspect that all of those weren’t malice as much as neglect but for such a large company it’s definitely not a lack of resources if they choose not to test on browsers they don’t make. The real damage, however, was not things actually breaking but the constant push to use Chrome. If you used Firefox you would be prompted to do that frequently visiting Google search, mail, YouTube, etc. with various allegations of better performance which didn’t hold up in testing.

khimaros 3y ago

cloud console is unusably slow in Firefox