Fourth [LWN.net]

Fourth

Posted Dec 17, 2025 6:32 UTC (Wed) by ebee_matteo (guest, #165284)
In reply to: Fourth by dskoll
Parent article: Mozilla gets a new CEO: Anthony Enzor-DeMeo

As somebody using Firefox with Microsoft 365 and MS Teams daily, there are several small and annoying issues. Even to the point that editing a Word document jumps backwards in the text while auto-saving during typing. Or audio breaks down in calls for no reason. Or email writing in Outlook is janky.

SAP is another thing that only works in Chrome/Edge.

The majority of employees at European companies rely on Microsoft products for their business. That's million of users, 8 hours per day.

Sure, as a Linux embedded dev I am more than willing to take the pain to have a browser that doesn't resell my data. I can work around problems. I am also in the 1%. Corporate? They just want to reduce calls to the help desk hotline.

Fourth

Posted Dec 17, 2025 13:08 UTC (Wed) by ptime (subscriber, #168171) [Link]

I use O365 on Firefox Nightly every day and don’t have any issues

Fourth

Posted Dec 17, 2025 21:10 UTC (Wed) by mathstuf (subscriber, #69389) [Link] (4 responses)

I have definitely noticed jank in Teams on Firefox, but I'm going to blame it all on Teams. I don't know what it is like recently because I've been using a macOS machine for video calls (still Firefox though; everything I've tried works fine) because Dell "wisely" used IPU7 camera hardware in this model which works poorly on Linux.

My observations were once:

- everything except video working with uBlock enabled
- if there is a whiff of a Microsoft login cookie, I was blocked because "Teams was disabled for my account" (nevermind that anonymous users could join the call…)
- in private browsing, the login page would infinitely redirect
- in a normal session (fresh-ish profile), it mostly worked (I think background blurring/replacement wasn't supported at the time)

Fourth

Posted Dec 17, 2025 21:21 UTC (Wed) by mb (subscriber, #50428) [Link] (3 responses)

> but I'm going to blame it all on Teams

Yes. That's the problem.

Firefox used to work perfectly fine between say about 2010 - 2020, roundabout.
Now we are back to the bad old times where websites only work correctly with certain browsers.

The answer to that is *not* to just ignore it and say it's somebody else's fault.
Even if in fact it *is* somebody else's fault.
That doesn't help Firefox.
It kills it.

And to the people saying that it's plugins/ublock that break sites:
No, it's not. Almost never does disabling ublock unbreak sites.
This is a fundamental problem.

Fourth

Posted Dec 17, 2025 23:33 UTC (Wed) by ptime (subscriber, #168171) [Link]

I was trying to rent a storage unit today, the site was “broken,” and turning off UBO fixed the site.

Fourth

Posted Dec 17, 2025 23:39 UTC (Wed) by pizza (subscriber, #46) [Link] (1 responses)

> The answer to that is *not* to just ignore it and say it's somebody else's fault.

Pray tell, WTF is Mozilla (or indeed, any of us) supposed to do about Microsoft deliberately choosing to degrade functionality on browsers (and/or platforms) other than their own? What will making Firefox into yet another Chrome reskin accomplish?

None of us use Teams _willingly_. Instead it's a requirement for $dayjob. Complain and at best you'll be either ignored -- more likely you'll just be told to "use the app or other supported platform" [1] and/or get written up for violating IT policies. [2]

[1] my new employer's SSO requires Chrome or Edge along with a couple of plugins in order to even _log in_.
[2] processing company data with unapproved software

Fourth

Posted Dec 18, 2025 9:37 UTC (Thu) by tzafrir (subscriber, #11501) [Link]

For me video calls are broken with Firefox and work with Chromium: both on Teams and on Jitsi (and on a trivial html demo file I tried, to see using a camera). This started recently, not sure exactly when. Maybe related to playing with libcamera, and maybe related to another upgrade. Have not had the time to debug this further. Video calls have generally worked better with Chroium than with Firefox: this is not just an issue with Teams.