If you look on the mozilla bugtracker, there are many people having this same issue
A profile can make a bug with vague or difficult steps to reproduce surprisingly actionable.
So I use it in a tab on Firefox. Much smoother.
Sounds like user agent / window.navigator sniffing in order to block the browser.
Classic microsoft. They will never change.
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.
how is that firefox problem if the service is actively hostile towards 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.
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.
AWS Console being completely stateful with its accounts and roles is only usable in Firefox with Containers.
And as for Google Maps I don't see any difference between Chrome and Firefox.
I use Confluence for work, and so have to use Chrome. It's slow and terrible everywhere.
Brave: 8.46s Firefox: 26.91s
Same machine, an older thinkpad (i5-6300U). I posit that the perf differences may be masked by newer hardware.
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.