4 ms·

MS Teams doesn't support Firefox: https://learn.microsoft.com/en-us/microsoftteams/unsupported-browsers https://learn.microsoft.com/en-us/microsoftteams/unsuppo

MS Teams doesn't support Firefox: https://learn.microsoft.com/en-us/microsoftteams/unsupported-browsers https://learn.microsoft.com/en-us/microsoftteams/unsupported... Or the VMware console: https://bugzilla.mozilla.org/show_bug.cgi?id=1769175 https://bugzilla.mozilla.org/show_bug.cgi?id=1769175 There's probably a bunch of other web apps that exclusively support Chromium-based browsers, unfortunately.

gumballindie 3y ago
Why would anyone want to use ms teams? I understand employers stuck in the fax age might demand it but it’s their problem if they want their data leaked. For personal and outside work no one should use ms teams.
- shiroiuma 3y ago
  Companies like to use Teams because it's basically free: they already subscribe to Microsoft's Office365 services, and Teams comes with it. To use a competitor, they'd have to pay for that separately. "Teams is shitty and buggy" isn't enough of a justification to convince upper management to shell out big bucks for licenses for something like Zoom when they're already getting Teams effectively for free.
mikkelam 3y ago
I mean, it's not that bad to jump into chromium once in a while
mrtksn 3y ago
Chrome really has become the new IE. That's sad.
- FirmwareBurner 3y ago
  It's even worse than IE was in it's day. At least IE back then was just a monopoly and not also a giant spy machine for an ad empire.
  - Longhanks 3y ago
    No, it's objectively not worse, you can compile Chromium yourself and remove any features you don't want, something you were never able to do with IE.
    - mrtksn 3y ago
      I don't think not having enough versions of IE was ever a problem. The problem starts when everyone builds their app to a platform that is very dominant and controlled by people who's interest are not always aligned with the user's interests. You don't have to compile Chromium to have a browser incompatible with the websites that people build for Chrome, you can just use Firefox or Safari or write your own browser if you want to have a web browser that won't be able to run Microsoft Teams.
    - FirmwareBurner 3y ago
      Chrome != Chromium. The vast majority of the planet is using Chrome, not Chromium. Most average joes have no idea about Chromium. Either way, whether you're using Chromium or Chrome, you're still entrenching Google's monopoly over the web. Like the sibling said, the problem was IE's monopoly itself not the lack of more IE-based variants which wouldn't have helped at all, the same way how Chromium isn't helping counter Google's monopoly.
- Dah00n 3y ago
  IE held back the development of the WWW. That would be the spot Safari has today. What Chrome is doing is much worse, since it is strangling the web, not just holding back new features.
  - mrtksn 3y ago
    Not true at all, IE what is the most innovative browser until it wasn’t. For example They invented Ajax, One of the core technologies that made the web what it is today.
    - zlg_codes 3y ago
      They invented ActiveX object and the accompanying XmlHttpRequest that AJAX would later morph into, and then change the X part (XML) to JSON. While it was innovative, I would argue it's made the Web worse, given the impact of Javascript and surveillance on the Web.
nimbius 3y ago
i mean just because they arent supported doesnt mean they dont work just fine. the vmware bug is 2 years old. honestly slowing down updates for adblockers sounds like a dangerous idea. sooner or later, someone will send you to court for an appstore monopoly, and sooner or later youll lose that case. in the meantime people lose interest in your ecosystem because of the increasingly predatory chicanery that makes their browsing experience suck. sending more eyes to firefox makes firefox better. eventually, better than even you. This all smacks of "we've tried nothing and we're all out of ideas." Manifest V3 is dead on arrival if youre going to bury the average google user in an avalanche of unskippable ads and full screen GPU testers. nobody wants this modern hell, and you've everything in your power to reform or amend it to dial back the surveillance capitalism and hyper consumption.
- johnnyanmac 3y ago
  Yeah, I only use Chrome once in a blue moon and have had a few dozen interviews through teams on web. Haven't had a problem yet (or, no more problems than Google meet/Zoom). My last role used teams on the day to day and Chrome wasn't even installed on my work machine.
matheusmoreira 3y ago
Unsupported browsers in 2023? Shame on them.
- astura 3y ago
  They only did this in the last 6 months or so. I used to use Firefox with Teams meetings until recently.
mwexler 3y ago
The Teams doc from Feb 2023 is a bit out of date, or is just legal cya. Still limitations, but I joined a Teams meeting the day before this comment with my microphone and external cam, and participated fully, using Firefox on MacOS. Yes, some client functionality is still missing (I didn't share a screen, for example), but both sides (MS and FF) appear to be making improvements.
- aquova 3y ago
  I use Teams fairly regularly in Firefox on Linux. Everything seems to work completely fine, with the exception of 1-on-1 calls. You can't send them, you can't receive them, and you can't even see when someone is calling you until the missed notification pops up. I have no idea why group calls work fine but those don't, but that's how it is.
bjackman 3y ago
I used Teams in Firefox for a couple of years. It was shit, but I'm pretty sure it would have been just as shit in Chrome.
heftig 3y ago
Slack calls and "huddles" still do not work in Firefox, either. Way back before huddles were implemented it used to work. Then they broke it and now it's Chromelike-only.
g105b 3y ago
I can use Teams perfectly on Firefox by switching my User Agent to Chrome. It's a weird decision MS have made.
loloquwowndueo 3y ago
You can still use Chrom* for those crappy sites and Firefox for everything else.
bryanrasmussen 3y ago
not supporting a particular browser just means that if a bug report comes up about your product with that browser then nothing gets done, but since everyone develops towards standards bugs in FF will probably be minimal, especially if they do support Safari (because unlikely something does not work in both Safari and Chrome) also the Teams link describes ways to work around limitations with teams on a particular browser that does not support the teams web app, which is what the article says FF etc. does not support.

gumballindie 3y ago

Why would anyone want to use ms teams? I understand employers stuck in the fax age might demand it but it’s their problem if they want their data leaked. For personal and outside work no one should use ms teams.

shiroiuma 3y ago
Companies like to use Teams because it's basically free: they already subscribe to Microsoft's Office365 services, and Teams comes with it. To use a competitor, they'd have to pay for that separately. "Teams is shitty and buggy" isn't enough of a justification to convince upper management to shell out big bucks for licenses for something like Zoom when they're already getting Teams effectively for free.

mikkelam 3y ago

I mean, it's not that bad to jump into chromium once in a while

mrtksn 3y ago

Chrome really has become the new IE. That's sad.

FirmwareBurner 3y ago
It's even worse than IE was in it's day. At least IE back then was just a monopoly and not also a giant spy machine for an ad empire.
- Longhanks 3y ago
  No, it's objectively not worse, you can compile Chromium yourself and remove any features you don't want, something you were never able to do with IE.
  - mrtksn 3y ago
    I don't think not having enough versions of IE was ever a problem. The problem starts when everyone builds their app to a platform that is very dominant and controlled by people who's interest are not always aligned with the user's interests. You don't have to compile Chromium to have a browser incompatible with the websites that people build for Chrome, you can just use Firefox or Safari or write your own browser if you want to have a web browser that won't be able to run Microsoft Teams.
  - FirmwareBurner 3y ago
    Chrome != Chromium. The vast majority of the planet is using Chrome, not Chromium. Most average joes have no idea about Chromium. Either way, whether you're using Chromium or Chrome, you're still entrenching Google's monopoly over the web. Like the sibling said, the problem was IE's monopoly itself not the lack of more IE-based variants which wouldn't have helped at all, the same way how Chromium isn't helping counter Google's monopoly.
Dah00n 3y ago
IE held back the development of the WWW. That would be the spot Safari has today. What Chrome is doing is much worse, since it is strangling the web, not just holding back new features.
- mrtksn 3y ago
  Not true at all, IE what is the most innovative browser until it wasn’t. For example They invented Ajax, One of the core technologies that made the web what it is today.
  - zlg_codes 3y ago
    They invented ActiveX object and the accompanying XmlHttpRequest that AJAX would later morph into, and then change the X part (XML) to JSON. While it was innovative, I would argue it's made the Web worse, given the impact of Javascript and surveillance on the Web.

nimbius 3y ago

i mean just because they arent supported doesnt mean they dont work just fine. the vmware bug is 2 years old. honestly slowing down updates for adblockers sounds like a dangerous idea. sooner or later, someone will send you to court for an appstore monopoly, and sooner or later youll lose that case. in the meantime people lose interest in your ecosystem because of the increasingly predatory chicanery that makes their browsing experience suck. sending more eyes to firefox makes firefox better. eventually, better than even you. This all smacks of "we've tried nothing and we're all out of ideas." Manifest V3 is dead on arrival if youre going to bury the average google user in an avalanche of unskippable ads and full screen GPU testers. nobody wants this modern hell, and you've everything in your power to reform or amend it to dial back the surveillance capitalism and hyper consumption.

johnnyanmac 3y ago
Yeah, I only use Chrome once in a blue moon and have had a few dozen interviews through teams on web. Haven't had a problem yet (or, no more problems than Google meet/Zoom). My last role used teams on the day to day and Chrome wasn't even installed on my work machine.

matheusmoreira 3y ago

Unsupported browsers in 2023? Shame on them.

astura 3y ago
They only did this in the last 6 months or so. I used to use Firefox with Teams meetings until recently.

mwexler 3y ago

The Teams doc from Feb 2023 is a bit out of date, or is just legal cya. Still limitations, but I joined a Teams meeting the day before this comment with my microphone and external cam, and participated fully, using Firefox on MacOS. Yes, some client functionality is still missing (I didn't share a screen, for example), but both sides (MS and FF) appear to be making improvements.

aquova 3y ago
I use Teams fairly regularly in Firefox on Linux. Everything seems to work completely fine, with the exception of 1-on-1 calls. You can't send them, you can't receive them, and you can't even see when someone is calling you until the missed notification pops up. I have no idea why group calls work fine but those don't, but that's how it is.

bjackman 3y ago

I used Teams in Firefox for a couple of years. It was shit, but I'm pretty sure it would have been just as shit in Chrome.

heftig 3y ago

Slack calls and "huddles" still do not work in Firefox, either. Way back before huddles were implemented it used to work. Then they broke it and now it's Chromelike-only.

g105b 3y ago

I can use Teams perfectly on Firefox by switching my User Agent to Chrome. It's a weird decision MS have made.

loloquwowndueo 3y ago

You can still use Chrom* for those crappy sites and Firefox for everything else.

bryanrasmussen 3y ago

not supporting a particular browser just means that if a bug report comes up about your product with that browser then nothing gets done, but since everyone develops towards standards bugs in FF will probably be minimal, especially if they do support Safari (because unlikely something does not work in both Safari and Chrome) also the Teams link describes ways to work around limitations with teams on a particular browser that does not support the teams web app, which is what the article says FF etc. does not support.