Skip to content

Instantly share code, notes, and snippets.

@jacobrossi
Last active April 1, 2018 01:29
Show Gist options
  • Save jacobrossi/c9699b27df2f4e97c0bd to your computer and use it in GitHub Desktop.
Save jacobrossi/c9699b27df2f4e97c0bd to your computer and use it in GitHub Desktop.
Windows 10 Technical Preview IE UA String
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0
@nickshanks
Copy link

@triblondon I presume the IE team have found that the number of extant sites where a naïve UA detection is used as feature selector outweigh (both in quantity and collective importance) the sites that use both explicit feature detection coupled with UA identification to exclude UAs with buggy implementations. That this hinders future interoperable website development is a trade-off they were willing to make.

@dmethvin
Copy link

See this blog post for the crazy UA sniffing that some people do, it's no wonder IE has to mention every browser. I agree that UA sniffing can be useful in some cases. The problem is that it's been abused and the abusers have fled the scene or just don't care, leaving the browser makers to fiddle with the UA so their users don't suffer. It's not just IE either, Chrome mentions Gecko and Safari for a reason.

@victor-homyakov
Copy link

Microsoft, be brave! Let it be just "Edge/12.0"!

@silverwind
Copy link

Can we please deprecate UA strings already?

Here's wishing for something like navigator.supports.{feature}.

@dmethvin
Copy link

@jrodl3r
Copy link

jrodl3r commented Jan 22, 2015

@silverwind after they all agree to do that in 10 years, IE will insist on using different feature-names.

@lyzadanger
Copy link

There must be an entire field emerging: UA archaeologist and lore historian. It's starting to read like the "begats" in the bible. All browsers much connect their lineage to Konqueror or face a lack-of-legitimacy crisis!

@jacobrossi
Copy link
Author

Honestly, we wish the UA string didn't have to be a lie (though it is in every browser). If the tokens were stickers, then this looks like the back of my laptop! But this is a necessary change. The reality is that our new engine, EdgeHTML, is further diverged from Trident than even Blink is from WebKit. So its necessary to break those ties. Further, today's web just doesn't work unless you have these other tokens. The number of broken sites is in the thousands. It's also worth noting that we're not just slapping these in there with nothing else, these Chrome/Safari tokens come along with a commitment to quadruple down on interoperability with these browsers. To date, we've made over 3000 interop fixes and are adding over 40 new standards, which makes these tokens more of a white lie. :) Rest assured we understand sniffing is occasionally necessary. We will absolutely maintain a way to confidently identify the new engine (look for "Edge").

@z-eh
Copy link

z-eh commented Jan 24, 2015

It's just some compatibility issue. We have Mozilla keyword in IE UA string from IE9, now we also have Safari and AppleWebKit for the same. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment