5 ms·

Does using `window.navigator.userAgent` still work? Does it still return the actual user-agent? Yes, and because it does, people will use it. You (or standards

Does using `window.navigator.userAgent` still work? Does it still return the actual user-agent? Yes, and because it does, people will use it. You (or standards) bodies can scream from the top of the mountains that it's deprecated, but it won't matter, because if it's there, it will be used.

Szpadel 4y ago
but Microsoft should understand why this is an issue, they had to rename their windows from 9 to 10 because applications did check based on os name string and just exit after detecting it contains "windows 9" as it suppose to match windows 95 and windows 98
- capableweb 4y ago
  Microsoft is a huge corporation with multiple different identities inside of it, like every international super-conglomerate. The people who work on the OS are very different people who work on the web stuff.
- ivandenysov 4y ago
  Where can I read more about this?
  - Szpadel 4y ago
    I don't think that there was any well written article about as it was very plausible rumor. but you can see eg: https://searchcode.com/?q=osname.startswith%28%22windows+9%22%29 https://searchcode.com/?q=osname.startswith%28%22windows+9%2... to see this issue present in a lot of publicly available source code.
    - MikusR 4y ago
      Quick look and most of those results are checking for macosx version or really old code where the only windows is 95 and not even xp.
- cpeterso 4y ago
  Similarly, Mozilla recently had to freeze part of Firefox’s User-Agent string because some websites mistook Firefox 110 as IE 11 and blocked access because they no longer supported IE 11. The websites misinterpreted “rv:110” in Firefox’s Use-Agent string as “rv:11”. https://bugzilla.mozilla.org/show_bug.cgi?id=1805967 https://bugzilla.mozilla.org/show_bug.cgi?id=1805967
deleted 4y ago
[deleted]
curtisblaine 4y ago
The alternative is breaking backwards compatibility, which means breaking the Web. (I'm not necessarily against that)

Szpadel 4y ago

but Microsoft should understand why this is an issue, they had to rename their windows from 9 to 10 because applications did check based on os name string and just exit after detecting it contains "windows 9" as it suppose to match windows 95 and windows 98

capableweb 4y ago
Microsoft is a huge corporation with multiple different identities inside of it, like every international super-conglomerate. The people who work on the OS are very different people who work on the web stuff.
ivandenysov 4y ago
Where can I read more about this?
- Szpadel 4y ago
  I don't think that there was any well written article about as it was very plausible rumor. but you can see eg: https://searchcode.com/?q=osname.startswith%28%22windows+9%22%29 https://searchcode.com/?q=osname.startswith%28%22windows+9%2... to see this issue present in a lot of publicly available source code.
  - MikusR 4y ago
    Quick look and most of those results are checking for macosx version or really old code where the only windows is 95 and not even xp.
cpeterso 4y ago
Similarly, Mozilla recently had to freeze part of Firefox’s User-Agent string because some websites mistook Firefox 110 as IE 11 and blocked access because they no longer supported IE 11. The websites misinterpreted “rv:110” in Firefox’s Use-Agent string as “rv:11”. https://bugzilla.mozilla.org/show_bug.cgi?id=1805967 https://bugzilla.mozilla.org/show_bug.cgi?id=1805967

deleted 4y ago

[deleted]

curtisblaine 4y ago

The alternative is breaking backwards compatibility, which means breaking the Web. (I'm not necessarily against that)