Microsoft Teams (free) not compatible
-
Given that ms will need lots of publicity to compete with existing team management tools, it seems kind of dumb to lock people out based on their browser of choice.
-
@lonm Depends what browsers they lock out. If it's only Vivaldi users, they aren't missing out on much
-
I already mentioned it in another thread, of teer that using a use agent switcher to be able to use a perfectly compatible web page, it is outrageous and an insult to the user.
I think this is due to two causes, a useless webmaster or due to commercial interests to exclude an uncomfortable competitor that does not include third-party codes from Google and MS.
I think these Browser sniffers should be oriented to the real capabilities of the browser or disappear completely. -
Known as
VB-39154 - "Microsoft Teams spoof"I've linked this thread to the bug.
-
@luetage said in Microsoft Teams (free) not compatible:
@lonm Depends what browsers they lock out. If it's only Vivaldi users, they aren't missing out on much
I just checked it out with Opera Dev, and it's not blocked with it for whatever reason.
-
The whole mindset of this discussion is kinda interesting. If some service or site doesn't work on a browser, who does the casual user blame, the website or the browser? I'd argue most blame the browser and move on. I don't think it makes sense at all to complain about the "stupid" webdevs/site admins/project managers who check the user agent and are responsible – most end users really couldn't care less. If you don't have the majority of users behind you (like chrome/firefox/safari), then you really don't have any influence, and no amount of name calling and blaming can change this. In a way the browser spoofing is the only thing Vivaldi can do.
-
@luetage said in Microsoft Teams (free) not compatible:
webdevs/site admins/project managers who check the user agent and are responsible
I don't even think that's it either. In all likelihood is some third party library they use to check that browsers have the latest version and it rejects anything unexpected.
I certainly wouldn't want to implement user agent checking when I can get someone else to do it for me.
In that case most people will still blame the browser. Some blame also lies with the third party too, though.
One solution to these cases is to just increase the user share of the browser so Devs recognise it.
But that won't happen if people are turned away from using the browser because it's not recognised enough...
-
@lonm You come to the same conclusion. It's a circular argument.
-
@lonm said in Microsoft Teams (free) not compatible:
and it rejects anything unexpected.
That is the bit I don't understand! Why not just give a message -
We haven't tested with the browser you are using and will not support you if there is a problem - do you wish to continue anyway?
-
@tbgbe That's something that would make sense...
-
@tbgbe I wish they would do that too. I wonder if maybe there's some sort of unspoken convention forming.
"I saw site X block old browsers, so I'll do it on my site Y too"
-
@quhno said in Microsoft Teams (free) not compatible:
Known as
VB-39154 - "Microsoft Teams spoof"I've linked this thread to the bug.
Boggles the mind, here in August. Why wasn't this a simple 10-second edit of whatever the master browser.js is these days? I can understand why the tough problems are never solved (stacks, I'm looking at you), but THIS?!
-
Worth noting:
https://forum.vivaldi.net/topic/13795/microsoft-teams-unsuported-browserAlso worth noting, from the 2.0 release notes, proving that the extremely heavy lifting of adding a line of spoofing is actually done on occasion:
"UA spoof meet.google.com VB-39784" -
Done, but wow, I have to conclude these months later that Vivaldi doesn't have a browser.js-like system. That's amazing.