>Teams are broken under Firefox
>change useragent to egde/chrome
>it works now
Thank you Microsoft.
The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
41–50 of 143 posts
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#42In retrospect, wasn't putting "Mozilla" in your user-agent string when you aren't the Mozilla Foundation or project a trademark violation, that they could have enforced?
You can't use trademark in that way if they would need it for compatibility. Nintendo made games have a "nintendo" title scroll on Gameboy and checked for it as "genuine cartridge" protection in a special chip, and sued third parties for trademark violations if they included the title scroll to get around the protection chip. Courts ruled Nintendo couldn't use trademark in that way, that it was laundering in more rig…
Do you have sources for such rulings? I'm only aware of the very similar https://en.wikipedia.org/wiki/Sega_v._Accolade.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#43I know it would be a temporary disaster but I think at this point I wish Safari, FF, Chrome and Edge would just decide on a flag day to get rid of user agents. From March 17th, 2023 (or whatever) all user agent strings are now “WebBrowser/1.0” until the end of time. Just force the switch to better methods.
They had an opportunity to do that with HTTP/2, /3, but they kept the User Agent. It's a bit different, but it's still there.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#44>Teams are broken under Firefox >change useragent to egde/chrome >it works now Thank you Microsoft.
This is just anti-competitive practice, yes? Presumably unlawful.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#45Earlier quoted context omitted.
They would have passed on the trademark rights with the rest of the IP
I’m on mobile so kinda limited search capacity, but it looks like IE was using “Mozilla” in its UA string for a couple years before the trademark was published (granted it was filed a few months prior to that IE release, and granted I have no idea how to read uspto.gov with any confidence that I understand it, and also granted I have no idea how much prior usage of trademarks overlaps with concepts like prior art for…
It could be passing-off which is an unregistered right (in UK at least) as they were using that mark to pretend to be another product.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#46So rv0110.0 would not work?
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#47Earlier quoted context omitted.
They would have passed on the trademark rights with the rest of the IP
I’m on mobile so kinda limited search capacity, but it looks like IE was using “Mozilla” in its UA string for a couple years before the trademark was published (granted it was filed a few months prior to that IE release, and granted I have no idea how to read uspto.gov with any confidence that I understand it, and also granted I have no idea how much prior usage of trademarks overlaps with concepts like prior art for…
[deleted]
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#48Stop sending User-Agent. Replace it with nothing. Not client hints. Nothing.
If sites start rejecting Firefox clients because of that, then instead change it to send exactly the same User-Agent (and other software identification) that Chrome sends, and commit to exactly faking Chrome's signals in the future.
The UA header never had any business existing to begin with. Servers guessing client capabilities from the software they're running, or trying to work around client bugs, is architecturally insane, concentrates power excessively, and guarantees that morons will write bugs like the one this story is about. And the other uses of the information are simply evil.
If you need to signal specific capabilities, which you generally should not be doing because you shouldn't have punted all real attempts at standardization years ago, then signal specific capabilities. Or let the server try stuff and give only success or failure feedback.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#49So rv0110.0 would not work?
I presume that would unfortunately break websites in _other_ ways, if they're UA-sniffing Firefox in unconventional ways. At that point they might as well remove it altogether instead of drastically changing the UA string.