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.
This is still under review by the feature team. No new details yet.
Alexander Kuznetsov commented
Yandex browser is the 2nd popular browser in Russia. It has 21% share on desctop and 10% at the mobile. It's Chromium based and Teams doesn't support it.
Thanks for responding, v-brorob. It's my experience that Microsoft Teams works great on Chromium when spoofing my User-Agent as Chrome on Windows, so while I understand that advertising Chromium support is just going to cause headaches for the developers, I'd rather see Teams try to load on unsupported browsers (and maybe warn the user about it) and fail a fraction of the time than fail all the time without trying.
Vilém Jeniš commented
Vivaldi browser uses blink. Chrome uses blink. Chrome is suported. vivaldi is not...
Please refrain from the 90's practice called 'Browser detection' and use what's called 'Feature detection' or polyfills.
Why do you classify Vivaldi as unsupported? Why don't you let me run the app in my browser anyway? I won't report bugs if they only occur in my browser...
Adminv-brorob (Admin, Microsoft Teams) commented
teams.microsoft.com doesn't work with Chromium
Could you remove the browser check from the web version of teams, and use feature detection instead?
I use Chromium (the open source build of Chrome) which currently gives me:
"Hmm. Your browser version isn't supported. Here's what works:"
Right now I'm using Firefox to access your site, but I'd rather not have the overhead of a second browser just to access your service.
Spoofing the UA doesn't work, which is expected as my UA already contains the "Chrome/56.x.y"
FWIW, office 365 nor consumer skype has this restriction.
Morgan Touverey Quilling commented
YES! Please! I have to keep Chrome and Chromium opened at the same time. Please do something, a 10-mins hotfix on your side will save us a lot of frustration. It's not 2005 anymore, please stop aggressive User-Agent sniffing.
Same with Opera and Vivaldi. By all means throw a warning, but always allow the user to accept and continue.
I thought we'd got past silly browser specific web sites?
ed eliott commented
On linux chrome's user agent is chromium and works just fine - please don't block unsupported browsers but maybe say "we don't think it is suppported but give it a try here" - that would be awesome.
Access Webapps in a tab works fine in the desktop version. However many team members want to use the channels during travel in the browser. The browser tells us that the page can't be opened in a frame.
Please make user experience as unified as possible at least in MSFT based workspaces, but better also on IPad (app and Safari). That will improve the adoption over larger communities.
Ole Markus With commented
The latest Version of Seamonkey 2.46 is locked out of Teams whilst it works just fine with the rest of O365/SPO (under Windows 7 and LinuxMint 13 and 18/Lubuntu 16.04)
SeaMonkey is basically just Firefox wrapped in a more traditional UI so underneath it is just as capable as Firefox is.
Vivaldi and Opera area also locked out and these are both based on Chromium so have pretty much the same feature set as Chrome.
Amit Wason commented
Same issue on Android Chrome / Firefox - annoying as the Teams App will not work in landscape mode so I thought I'd just use Web Access...nope!
Chromium is affected by this. Please just use feature detection.