Mozilla/5.0 (Windows NT 6.1 WOW64 Trident/7.0 AS rv:11.0) like Geckoīasically they were trying to solve the problem of “now that we’ve invested seriously in web standards, how do we get access to content that makes use of those features, and still have a detectable version number for analytics (or whatever).
Mozilla/5.0 (compatible MSIE 10.0 Windows NT 6.2 Trident/6.0) Here’s the IE10 UA, which followed the same-ish predictable pattern they had since IE 2.0: Presumably in an attempt to unburden itself from a legacy of UA-sniffing-driven workarounds for a browser that hadn’t historically supported a lot of useful things (like WebGL, or some ES5 or ES6 stuff - I don’t really remember and can’t be bothered to look it up), the IE team decided to change up their User-Agent string back in 2013. So why did Mozilla just freeze rv:109.0 in the User-Agent string? Perhaps forever, or just perhaps until Firefox 120 is released? If you didn’t, take note that rv:109.0 did not change in the second one-but Firefox/110.0 did. If you managed to visually discover the difference (I guess in the world’s lamest “Spot the Difference” game), congrats. Mozilla/5.0 (Macintosh Intel Mac OS X 10.15 rv:109.0) Gecko/20100101 Firefox/109.0Īnd as of last week, the UA string in Firefox for versions 110 and higher looks like so:
If you happen to be using Firefox Beta 109 on an overpriced MacBook Pro that has a sticky letter s today (the 29th of December, 2022), this is what the User-Agent string looks like:
0 kommentar(er)
