How can we make Microsoft Teams better?

Relax browser support check

The current browser support check is too pessimistic and prevents some modern browsers from loading Microsoft Teams. For example, up-to-date Chrome on Ubuntu Linux is not considered a supported browser, even though changing the User-Agent string to Chrome on Windows allows Teams to load without any problems.

Please consider a) just letting the browser try to load Teams, b) using feature detection instead of the User-Agent string, or c) blacklisting known broken browsers instead of whitelisting if the User-Agent string is used.

263 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    82 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        Chrome uses Blink. Vivaldi uses Blink. Please for the love of the gods. STOP the browser detection.

      • Josh commented  ·   ·  Flag as inappropriate

        I'm using Vivaldi. Just pop me a warning that it hasn't been tested in my browser, and you're still covered.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Could you please just remove the insane browser check right now.
        Then take your time to implement something which doesn't seem to be too high on your product backlog.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Come on, get this fixed. There is no good reason to block Chromium based browsers.

      • Jack commented  ·   ·  Flag as inappropriate

        This needs to be expedited fast. I'm steadily losing my respect for Microsoft and any developers that work there. However, there wasn't much respect to begin with.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Idea submitted nearly two years ago, under review for two months, no visible movement and nothing on the roadmap ... simple fact is, some of us use browsers like Vivaldi for accessibility reasons (something Vivaldi is far superior to IE, Edge and Chrome in), failing to relax the browser detection from methods Microsoft themselves have recommended as obsolete for better part of a decade and enable support of modern compatible browsers via proper feature detection is locking users out of this tool - and having something that affects accessibility "under review" or "on the roadmap" in 2018 is just not good enough!

      • Anonymous commented  ·   ·  Flag as inappropriate

        This whole user-agent detection is frustrating. Modern website should simply just work on modern browsers. Feature Detection, feature detection, feature detection... There are whole libraries you can use.

        Vivaldi is uses blink, Chrome uses blink. But I can't use Vivaldi because your **** user-agent detection does not like my GUI of choice.

        This thread has been around for awhile with no changes. Which means that MS does not give a ****. UGH!

      • Steinar Bang commented  ·   ·  Flag as inappropriate

        Vivaldi uses the Blink rendering engine so the "You're browser is not supported" message seems rather silly.

      • Philipp commented  ·   ·  Flag as inappropriate

        I had to override the user-agent string of Vivaldi on Linux via a command line argument to the browser, a few extensions that I tried don't suffice because they apparently do not modify the user-agent string on *all* outgoing requests. I suspect some XHR stuff still using the built-in UA, but all that is a whole different story.

        After forcing the user-agent string to some recent Chrome-on-Windows-10 variety, I was able to launch teams without running into that "Unsupported browser" page.

        Using a browser detection like that very much feels like 1995 and a modern webapp should not have to rely on such an abomination. Like the thread initiator pointed out: locking out old browsers for example is fine, but whitelisting is an absolute no-go in 2018.

      • Anonymous commented  ·   ·  Flag as inappropriate

        "Unsupported Browser" is nonsense and harkens back to the bad-old-days when web pages and browser didn't conform to standards. The solution is simple: MAKE YOUR SITE CONFORM TO ACCEPTED STANDARDS! We know that's not the "Microsoft Way", but it's a good idea if you want us to use your products.

        I'm using Pale Moon browser right now, spoofing the User Agent, and everthing works. Stop with the proprietary nonsense. Thank you.

      ← Previous 1 3 4 5

      Feedback and Knowledge Base