4 ms·

>Teams are broken under Firefox >change useragent to egde/chrome >it works now Thank you Microsoft.

• pbhjpbhj 4y ago
  This is just anti-competitive practice, yes? Presumably unlawful.
  • bobse 4y ago
    This is Rajesh and welcome to Microsoft forums. Please install Microsoft Edge TM. Bye.
  • olliej 4y ago
    No, it's just standard web developer laziness. They haven't made it IE only, they just broke the less popular browser, and likely anything else that is not chrome/blink, because chrome/blink is the new IE: its bugs define "correct behavior" it shipping something means "it's standard", no different from the "IE is the internet" era (and just like chrome there was a long period where IE was the best browser, before devs started targeting it alone).
    • bobse 4y ago
      It does work correctly once you change useragent string though.
      • jeroenhd 4y ago
        I believe Firefox doesn't expose the audio device output picker, only letting you select a single output device (you can select one in the permission prompt, but changing it is difficult). Last time I looked into why Teams wasn't working right, that was the reason Firefox was still listed as unsupported, because this can easily miss up setups with conference call PCs hooked up to some fancy proprietary audio conferencing system.
      • olliej 4y ago
        yes, I said it's standard webdev laziness. Many aeons ago I worked on webkit, and the first step for a great many site compatibility bugs is "does it work with a Firefox ua string". Because it is always easiest to just check ie/new-ie and then useragent gate everything else, that is what happens. Which is why we keep getting sites requiring chrome (new ie) or ie (old ie) - it doesn't matter if the site is broken due to reliance on chrome behavior vs spec, what matters is devs coding to a single browser and considering any deviation to be a bug in anything else.
• deleted 4y ago
  [deleted]