Care to give any examples? I am not having any issues at all. Not only that, but I don't feel like FF is getting in my way somehow and that I should try a different browser.
Discord is broken on Firefox. It's fast when you restart it, but over a few days it turns into a slog to the point where if you click on a different channel, it takes over 20 seconds sometimes to load. Then when you type a message, you can only type about 5 characters before it locks up for another 20 seconds.
If you look on the mozilla bugtracker, there are many people having this same issue
If you would like to write home about this Discord problem, please consider filing Bugzilla bug report with a memory log from Firefox’s about:memory page and a performance profile using the Firefox Profiler:
MS Teams video and voice doesn't work at all in Firefox. Google "gadgets" don't work in mobile Firefox unless you spoof the user agent. There are also a handful of other sites I've run into where certain functionality only works in chrome based browsers. Sometimes, spoofing the user agent is enough to get it working in firefox.
> MS Teams video and voice doesn't work at all in Firefox
Actually, I noticed voice started working last month. I could see the video but not send mine, but it might in the future.
Please don't force Teams on anybody though, this is unacceptable in 2022 for a company like Microsoft when its alternatives have been working in Firefox for years.
It didn't work at all in Chromium too, because apparently it relied on the Widevine DRM on Chrome (?!). That's nuts. That's bullshit. If you don't have it, it fails with an obscure error message like "Unable to join the conference" without any reason. Good luck guessing why.
If video and sound don’t work in firefox it sounds more like a microsoft issue than a firefox issue. Webcam and Microphone APIs are following the standard and are well documented on MDN.
Sounds like user agent / window.navigator sniffing in order to block the browser.
Oh, it's absolutely Microsoft's fault. In this case they are using (or at least were) pre-standard chrome specific apis.
The problem isn't that Firefox is bad. It's that many site are designed specifically for chrome, and they don't bother testing against Firefox. And for the average user, all they really notice is thay some sites don't work in Firefox.
Which I what many here who worked through the IE dominance have been warning against - yet the only thing we hear is that other browsers are the “new IE”.
It's not. That doesn't change the fact that some sites work better on chrome. Just like some sites worked best in IE, back when that was the dominant browser.
My bank's internet banking page to pay multiple beneficiaries pages is a jumbled mess in Firefox. I haven't bothered to check why but I am guessing it's some grid layout issue. I did write to bank highlighting the issue. It's been over a year and still issue persists so I just switch to Chromium for internet banking.
I do have some sites which are consistently slower on Firefox than on Chrome. Chrome (and Edge) just feel all-round snappier (at least when "new", ie with few tabs open). The difference is not enough for me to switch my daily driver, though.
Things that come to mind that I use often:
* AWS console
* Google Maps
* Confluence
Hell, even the front page of Hacker News loads a bit faster on Chromium than on Firefox. Sure, the difference is negligible in absolute terms, but still. I get around 5-600 ms for Chromium, and around 8-900 for Firefox. Both running on X11/Linux 5.19-zen on a Ryzen 5650U with 32 GB of RAM.
I haven't used Chrome intensively in a long while, but I seem to me remember at the time (many years ago, on a Mac) it would slow to a crawl after a few days with many open tabs. I don't have any such issue with Firefox on Linux.
I just tried on my mobile. Chrome is much slower. Firefox is sub second, while chrome was a noticeable wait. I actually checked if I didn't have connection issues and opened a new private tab in Firefox to check.
Google Maps, I can confirm. It works, but it's noticably slow on Firefox. Tiles appear a tab bit slower, and street view navigation takes a fraction of a second to respond. It didn't stop me from using Firefox, but I can absolutely understand if someone finds it as a deal breaker if they use Google maps often.
Well I can't say I have ever experienced performance quite that bad myself. On my i7-2700K desktop I'm only seeing about 6s-7s each. Kind of hard to tell when maps is really finished loading though.
I share the experience with Maps, though I never see it these days as the G gets its own ungoogled-chromium sandbox and don't get to play with other domains here anyway.
If you look on the mozilla bugtracker, there are many people having this same issue