I use Firefox, and Google's sites are literally the only ones where I consistently have issues. There was a period of about a month this summer where Google Maps was just completely broken for me, the map wouldn't update at all when attempting to search or pan. There was recently a several day span where chat in Gmail had a 10+ second input lag due to some font-related JavaScript code spinning the CPU nonstop. It's literally gotten to the point where I keep a Chrome window open and use it exclusively for Gmail, Google Meet, YouTube, and Google Maps.
It's pretty obvious from the outside that supporting Firefox is not a product priority for Google. It also seems clear that it's in their best interest to have users choose Chrome over Firefox. My guess is that this likely emerges from a lot of very reasonable sounding local decisions, like "prioritize testing on browsers with the most market share," but it is convenient how those align with the anti-competitive incentives.
I've posted this here on HN numerous times over the years, and it's been a while since I last posted it:
Google is the new "Microsoft", they embrace, they extend, then extinguish. Look at their email offering, messaging offerings, they built on top of XMPP, then they pulled the plug eventually. Android is Linux based, but insanely proprietary, the app store is not open by any means, you're fully at their whims to get your apps on there. Chrome is basically the IE of old, implementing proprietary things or APIs that are not yet standard for Google products, and pushing out competing browsers.
Not to diminish the other sketchy stuff Google's doing, but I think the maps lag issue might actually be Firefox's fault. Whenever it happens to me WebGL stops working across all websites and restarting the entire browser fixes it. It's almost like when Firefox has been open a long time it just forgets how to use graphics acceleration.
The thing that bothered me is it didn't always happen, at one point there was performance parity, and things changed in a way that specifically worked worse in firefox.
Which means:
A) Firefox had bad webgl implementations(I didn't experience what you did, but I wont say it doesn't happen) and google added features that regressed the experience on other browsers.
B) Google knowingly made performance worse on Firefox, regardless of webgl implementations.
C) Google leverages its own browser to only test on their browser, to influence the market to have to use googles browser in order to use their services(not the same as the IE/Windows monopoly lawsuit, but sure smells like it).
It is fascinating, how the simplest things on websites can be made arbitrarily involved, convoluted, over-complicated. And how those over-complications can then serve as a credible deniability.
You're basically looking at testing being done on Chrome (because it is Google's, and because of its large market share), Safari (because it runs on a large percentage of completely exclusive platforms where the customer can't switch, and because of its large market share), and Edge (because there are still many corporations that do "Nobody ever got fired for choosing Microsoft" and lock down browser options to just Microsoft's offering).
At this point, Firefox is very much an also-ran on two axes: market share is tiny and nobody forces it on their captive audiences. We may as well ask why Google isn't optimizing testing on Opera, or Samsung Internet.
(There is also the issue of under-the-hood engine. Since so many browsers have converged on a few core and JS stacks, testing on one exemplar of that stack has a tendency to suss out bugs in the other stacks. Firefox still being its own special snowflake in terms of JS engine and core means it has more opportunities to be different, for good or for ill. So there's a force-multiplier testing the other browsers that one lacks testing Firefox).
I had the same Gmaps issue, I disabled LocalCDN for the site and panning etc worked again. Apparently the addon must be fixed to account for whatever they were doing.
I use Firefox across Windows, Mac, OpenBSD, and Ubuntu. I've not seen any specific issues with Google sites at all. I only really use Docs, Maps, and Youtube with any regularity but I've not really seen any of these issues.
It's clear Google is only testing for chrome engine and safari: which comprise 97% of the browsers being used. Would you increase your testing by 50% to thoroughly test for 3% of the market?
As I said, the decisions are locally reasonable. However, if not supporting Firefox potentially exposed my company to scrutiny over anti-competitive behavior, then, yes, I would absolutely invest in testing procedures to mitigate that.
It's also worth emphasizing that it isn't difficult to support Firefox. I'm pretty sure that many of the sites that I visit do so largely by accident. I do a fair bit of web development, and Firefox/Chrome compatibility has never been an issue in the slightest for me. You almost have to go out of your way to choose Chrome-specific APIs in order to break compatibility. How does virtually every other website on the internet manage it—from my bank to scrappy startups with junior developers coming straight out of bootcamps—while Google with all of their engineering talent and $100+ billion cash on hand just can't seem to make it work?
Serious question - does anti-competitive behavior even apply to open source? Also, it's the open source chromium, not necessarily the browser Chrome, that dominates the browser market. The largest players in the industry, except for Apple, have lined-up to support chromium. Firefox is going against the grain. Is it Google's job to help them with their mission? Loosely speaking, in anti-competitive scenarios you have to show how a significant faction of the consumers are being harmed. You're going to have a tough time with that one.
you have to show how a significant faction of the consumers are being harmed. You're going to have a tough time with that one.
I'm not a lawyer and can't speak to what qualifies as anti-competitive behavior in a legal sense. Qualitatively, Web Extensions Manifest v3 and Web Environment Integrity are clearly harmful to consumers in my opinion. The first significantly hinders ad blockers, and the second kicks down the ladder on building search engines and hinders competition in that space. Other browsers using Chromium as a base doesn't change the fact that Google almost unilaterally controls it, and Google has made it extraordinarily clear that they're interested in making decisions that prioritize their own best interests over those of their users. I don't see why Chromium being open source would absolve any responsibility here, especially when the open source project in question primarily exists to serve the interests of the profit center of a mega-corp. I deeply support open source software, and I'm glad that Chromium is open source, but being open source doesn't excuse behavior that is against the interests of users whether it qualifies as illegal or not.
I think you're going to have a tough time with Chromium seeing as how the likes of Microsoft and Canonical are contributing to the project. You're also going to have a tough time showing anti-trust when Google is working with Apple. I'm old enough to remember some famous anti-trust lawsuits where the plaintiffs had a much more solid case and still lost. In this case Google is literally working with the industry's largest companies. You're going to have a really hard time with that.
The thing is that Firefox is the biggest project for an independent fully open source browser not tied to a big commercial company. Google having almost a monopoly is not good for the users, because Google therefore has a lot of leverage to push certain browser technologies that mostly benefit them and not necessarily the users. It's important to have an independent browser that is not optimized for 1 particular company's technology and needs. So we can view the web from a somewhat more neutral view. And yes, I think it's Google's responsibility to adhere to the webstandards and at least test their stuff in Firefox so they adhere to this neutrality. Otherwise they are only providing their websites for the Chromium-web, and not the Open Web.
> Would you increase your testing by 50% to thoroughly test for 3% of the market?
I don't think you get to make these kind of cost cutting decisions when you're a vertically integrated mega-corp who also owns the browser with 65% of the market.
Here’s another way to answer that question: do Vimeo, Twitch, Netflix, Amazon Prime, Instagram, TikTok, etc. say “let them use Chrome” or do they manage to do entry-level browser testing? The cost increase is nowhere near 50% and clearly they aren’t willing to write off millions of users – only the company with a direct financial incentive does that.
Yes, Firefox’s market share has been declining but that’s substantially because Google spent billions of dollars marketing Chrome and promoted it heavily on YouTube, Gmail, Search, etc. Deciding not to test or optimize fits neatly into the same pattern.
It's hard to argue anti-trust when all these browsers are based on Chromium - which is maintained in part by Google, Microsoft, Opera, Vivaldi, Intel, ARM, and Canonical plus several volunteers.
Makes me wonder if it's the wrong strategy and what an alternative might be. In context, one might assume that Google will use the Chromium monoculture to... ahem more assertively deliver advertisements, which would be "a real dick move" as it goes. I don't know how a concerned citizen might bring attention to or possibly prevent the actualization of such a strategy by Google.
Google is the largest contributor. The others chose Chromium because making a browser that's compatible with all the bloated standards invented by Google would require too much effort.
Since they throw me "Google recommends Chrome!" adverts in my face for various of their services, even when using a chrome-based browser it's not a case of only testing for Chrome/Safari. It's active work against others.
It's pretty obvious from the outside that supporting Firefox is not a product priority for Google. It also seems clear that it's in their best interest to have users choose Chrome over Firefox. My guess is that this likely emerges from a lot of very reasonable sounding local decisions, like "prioritize testing on browsers with the most market share," but it is convenient how those align with the anti-competitive incentives.