Chrome is the new IE in terms of support. "Best viewed in Chrome"
Safari is the new IE in terms of weird bugs that no other browser encounters. Some of their web APIs like LocalStorage and IndexedDB still have odd quirks (but at least they're not completely broken any more).
Ye, i remember they mentioning this, and people i know confirm it works fine. It just doesnt work on my end. I do have firefox set up to be very private though ( no 3th party cookies and more )
That's definitely a part of it. All of the MS web platforms rely heavily on first and third party cookies. You can't even log in properly to Teams if your browser is in incognito/private mode.
Firefox even is hardcoded to present itself as "Chrome on Windows" when visiting Teams.
Chrome is becoming the modern Internet Explorer. "Oh, yeah, the site only really works in IE for some reason…"
Chrome is the new IE in terms of support. "Best viewed in Chrome"
Safari is the new IE in terms of weird bugs that no other browser encounters. Some of their web APIs like LocalStorage and IndexedDB still have odd quirks (but at least they're not completely broken any more).
Ye, i remember they mentioning this, and people i know confirm it works fine. It just doesnt work on my end. I do have firefox set up to be very private though ( no 3th party cookies and more )
That's definitely a part of it. All of the MS web platforms rely heavily on first and third party cookies. You can't even log in properly to Teams if your browser is in incognito/private mode.
Ye, ive added the needed exceptions for *.teams.com, lync and skype just to login…
Logged out Teams can cause some unexpected issues, like not being able to use Emergency Dialing.
[This comment has been deleted by an automated system]
That's gotta make the Microsoft dev team confused. How can they call out Firefox in Teams if it doesn't even identify itself as such?