These can range from popular extensions to smaller, more specific productivity extensions. As a specific example, there is a Zendesk extension that can help load all links you click load in a single instance rather than having multiple tabs. It uses Zendesk's built in tabbing system for tickets and is very helpful for workflow.

The problem is this is only a chrome extension, and no such thing exists for Firefox. This is one example but there are so many more, and more of those situations are happening over time.

That is a worrying trend. It means that the chrome browser has such a massive market share, that in a lot of cases worrying about Firefox compatibility isn't even a productive concern anymore. This will eventually end in life support compatibility such as developers putting up splash pages or in-page notifications for users to switch to a more compatible browser. I have already seen extremely rare instances of this, but not enough where I would consider it a concern yet, just an asshole move.

Google's massive market share is seriously worrying for Mozilla and other browser vendors.

I switched to Firefox from Chrome over 4 years ago and I was disappointed to find some of my favourite Chrome extensions weren't available. I plan to add support for those Chrome extensions in Dot Browser by implementing those APIs and making them work in Gecko/Firefox environment.

But sure, yeah, let's keep the Web Platform at early 2000s standards. Let's make everyone download apps from a small set of walled garden app stores. Let's force developers to submit to those app store review processes and potentially have their content blocked for whatever opaque whims the store has today (ever changing, with little chance for appeal!). And then they can just snoop on their users through the local, natively installed app, that has all the permissions granted under the sun because users don't read installation prompts. That's so much better for privacy.

I personally spend most of my time figuring out the Chrome-specific quirks that pages rely on which are non-standard, and the Chrome devs almost never fix before conjuring up some new, ill-defined "standard" that they ship to production before others have even had a chance to figure out the last three.

It's maddening, especially when you look at Google's not-so-sterling track record just with major new "standards" like Web Components, WebRTC and Pointer/Touch events, not to mention how often they ignore Chrome's spec bugs until the web is reliant on them, and other vendors have to change their behavior and the spec to match them. Folks always seem to ignore all of the trouble Google causes, and just think "ooh, shiny new toy! Google good!"

Just imagine trying to implement all of those "standards" while Google is constantly changing them, under-documenting everything, have no reference implementation aside from the one they ship that's deeply tied to Chrome, and expect you to work on their time frame. All while not fixing bugs in the last two new APIs they pushed out, while pushing out two more at the same time. You wonder if they're doing it on purpose so no matter what the "standards" say, they just wait for the web to become reliant on their bugs, and then everyone else has to figure the whole mess out for them, like glorified janitors.

And then you look at the backlog of things you'd like to have fixed instead of figuring out the latest interop issue with some quirk that has a crbug open for three years, and the new privacy APIs and features you'd like to push and you start to feel a bit burned out. So you hop onto HN only to see yet another comment like yours, acting like we're doing nothing at all except "chasing shiny baubles". It's enough to make me wonder whether people like you actually care about the web at all or just want more half-broken new APIs to complain about.

I don't hate Firefox. I don't want browser hegemony. But if Firefox is our last, best hope against a Chromium hegemony, then we're doomed. It's been a decade since Chrome surpassed Firefox in marketshare. Not once, in 10 years, has Mozilla expressed any sort of believable plan to turn the ship around. Mozilla is failing Firefox.

For ten years now we've been watching non-Chromium browser engines die off while complaining about this, with no new one able to really compete because of the gigantic web API footprint Chrome has championed.

But yeah, go on telling me how some UI changes in Firefox are responsible for all that is wrong with Firefox. I'm sure all of the users still who still can't use Chrome-WebRTC apps in Firefox care about that more.

It's YOUR job to care about Firefox. And as far as I can tell, not enough people at Mozilla care enough about Firefox to make up for going from #2 browser in the world to numbers comparable to (checks notes) Samsung Internet. You complain about having to follow Google's lead. You aren't just following Google anymore. Y'all have to follow everyone.

And don't even talk to me about WebRTC. You folks have had 10 YEARS to get an act--any act--together around WebRTC. Firefox's WebRTC performance has been notoriously bad for that entire time. So, wait, let me get this straight. You complain about having to bend over backwards to appease Google's way of doing things. But now you're complaining about a case where Mozilla steadfastly refused to bend over backwards for Google for a decade? Over the format of the SDP lines. Because that's a hill worth dying on. Get out of here.

The folks who actually care and work on non-Chrome browsers have been telling us for a decade that Google is not being a good faith player, and is creating an obvious browser engine mono culture. And instead of listening to them, you ignore them to defend Google instead.

You're the one who should get out of here, and educate yourself on this stuff first before you talk big about it. Go find out just what a mess WebRTC has been thanks to Google and its ever-shapeshifting "plan B" (and not just from Google's point of view). It helped kill two major browser engines already, and it certainly wasn't because they didn't try to work with Google to figure it out, or spend a lot of time trying to reverse-engineer it as it changed, or even just trying to import enough of Chromium into their own browsers to ship "plan B" themselves after Google remained silent.

And while I'd love to help you with your pet bugs, including such basic web functionality as "offloading large chunks of image processing to a web worker", I'm here diagnosing live web sites to find that Chrome shipped `event.path` before it was standardized, or haven't fixed three year old bugs with `text-underline-offset`: things that are breaking such hyper-advanced and unimportant functionality on the web as clicking on links and underlining text properly.

So tell me again how I'm wrong and Google's bugs don't affect other browsers. And how it's my fault that Google seems to ignore interop bug reports until they become issues on live pages, and then conveniently say "well, the web relies on this now, so you change the standards and your own browsers to follow suit now"? I guess I need to be flawless myself before I have any right to complain about their bad behaviour?

Do go on. Tell me more about your theories about what I and other Mozilla folks do with our time, and how Google and its defenders aren't making it harder for us to do what we'd really rather be doing for our users.

In addition to Mozilla, Apple (Safari) and Microsoft (Edge) also have significant participation in web standards. I'm really glad Firefox exists, and they definitely punch above their weight in the standardization process, but Microsoft and Apple are also serious participants.

(Disclosure: I work at Google, speaking only for myself)