I have never once had an issue with a website that was solved by opening it in Chrome instead. and I switched to firefox like three years ago. If firefox is so much less supported, I'm not seeing it at least
I can remember a single time I had to swap to Chrome for something, and it was three years ago, and involved some flavor of WebAssembly, I believe.
If anyone can point out a current website that is acting up under Firefox and not Chrome, please post it. I just want want to know that the "Firefox is inferior" argument isn't a decade old echo.
ZenDesk is another, related to their SSO logins.
Unfortunately once bitten I become twice shy. These kind of works-in-popular-browser circumstances pushed me to making my own browser navigation switcher, so I never have to worry about any one site again. Of course that also means that even if they fix it in Ff then I won't notice. (It also doesn't help that Manifest V3 has taken a while for me to support and Apple keeps changing things.)
Which has made a knock on effect that if I’m using Firefox and something doesn’t work - I very much wonder if it would work in Chrome.
It’s burned into my brain now.
IMO this isn't the argument. Firefox users aren't discussing superior or inferior, but sites that accidentally or purposefully break or over-optimize for Chrome, making Firefox users second class citizens.
I commented about YouTube and Google Suite on another thread, but your webassembly example reminds me of the GCP dashboard and in browser virtual machine, which is also horrible in anything but Chrome if you plan to use it day in day out. I was spending my life there for a few months, and sure enough a dedicated Chrome instance made my life a lot better.
It's still interesting to contrast my personal experience re: Firefox with everyone elses when it comes to the "Manifest V3 ! Abandon ship, but to where?" conversation.
I have no insight into Firefox' technical foundations, but to your point I've been using it since the IE days and never had critical performance issues or compelling reasons to use another browser short of company specific sites: Google properties is one: while Firefox works, Google has obviously no incentive to make it work better than Chrome, and potentially incentives for the opposite.
Companies' internal sites and tools are another: fixating on one specific browser has been an (unwise) long lasting trend, and for a company Chrome being backed by Google has a lot more appeal than Firefox. That was the same dynamic that cemented IE6 in it's position.
Perhaps Firefox missed the V8/electron train that would have made it in the same position as Linux: a platform to run other things on. But I don't know the history around that.
(I actually had that exact issue yesterday; I managed to do it on the Android app, and didn't think this was an issue with Firefox specifically.)
This is the only reason I keep the Slack "desktop app" around.
Firefox doesn't work well on Google properties (for obvious and non obvious reasons). It's decent, but in my experience it 's significantly slow and resource intensive in most of Google Suite and subpar on YouTube[0]. Useable, but definitely heavier than Chrome. I ended up with a dedicated Chrome instance for meet and Sheets.
Recently I found Notion to be more and more sluggish, it might be because of cache and other relics as I spend my life in Notion, but fresh Chrome instances behave better. All in all, Notion has become worse and worse, so it might be just part of that trend.
Many enterprise extensions currently won't work at all in Firefox. It's in no part Firefox's fault, and enterprise software has always been shitty, but this is becoming a reality to me.
[0] I don't have the link at hand, but it was notably due to Google intentionally screwing up Firefox last time I looked into it...
I'm sure I've seen a few things not work on FF, but not many, and likely things that would break on Safari too (I've had govt stuff just not work on tablet safari for sure).
Also Slack.