Now, why would Teams calls only work on Chrome and not Firefox? Is anyone aware of any technology constraints, or is it just Microsoft being dicks?

it's microsoft being dicks. install a plugin to send different user agent headers, and it works just fine.

(at least it did the last time i had the misfortune of using teams)

People use teams via the browser?
That's actually a thing?

Eh, ms being dicks, use a chromium browser since that's all they care about now.

@zlice Checking for user agent strings is pretty dumb anyway (at least for compatibility issues). It's not future proof at all.

Chrome probably works on accident, because Edge is based on Chromium :)

@C0D4 yes, i use teams in browser. (or rather - in rambox). firstly because i have to handle two distinct teams accounts side by side for work, and secondly because that glorified, borked-up-beyond-all-recognition slack-clone laden with spyware and bugs will NOT get installed on any of my devices, period.

especially since the desktop client is nothing more than a custom electron itself.

I work in video communication and we also have some permission problems with Firefox. Here’s one, for example: https://discourse.mozilla.org/t/...

@C0D4

People use teams v̶i̶a̶ ̶t̶h̶e̶ ̶b̶r̶o̶w̶s̶e̶r̶ ?

That's actually a thing?

@C0D4 Yeah what @tosensei said, multiple accounts. Because obviously that's not a feature in Teams... Just as multiple tabs makes all tabs reload...

@tosensei I'll try the user agent, thaaanks

@C0D4 Yes. I my org we Use Google but a few times per year we get invited to meetings with others and no one wants to download a Teams client just for that.

Shit - did they really block FF?

My main issue with Teams (we never use it apart from a 3rd party vendor meeting two times per year) in a browser is that I need to use incognito since it breaks entirely due to some old cookies.

I normally use Chrome but if I recall correctly I've used FF sometimes just to avoid the cookie issue.