In our experience Microsoft Edge runs best on the ‘WebKit’ code paths in these sites. This is not the best approach, as Microsoft Edge matches ‘WebKit’ behaviors, not IE11 behaviors (any Edge-WebKit differences are bugs that we’re interested in fixing). Over the past year, we’ve seen some UA-sniffing sites that have been updated to detect Microsoft Edge… only to provide it with a legacy IE11 code path. For example, the Modernizr library is a fantastic and simple way of detecting features. We recommend that web developers avoid UA sniffing as much as possible modern web platform features are nearly all detectable in easy ways.
(“or rather, a balancing act of adding enough legacy keywords that won’t immediately have old UA-sniffing code falling over, while still trying to convey a little bit of actually useful and accurate information.”) The userAgent property has been aptly described as “an ever-growing pack of lies” by Patrick H.
Mozilla/5.0 (Windows NT 6.3 Trident/7.0 rv:11.0) like Gecko The Edge team details this even deeper on their blog.Īll user agents strings contain more information about other browsers than the actual browser you are using – not just tokens, but also ‘meaningful’ version numbers. Internet Explorer 8 is a common point of frustration for developers, so they will frequently check if a user is using ANY version of IE, and disable features.
Often, lazy developers will just sniff for the UA string and disable content on their website based on which browser they believe the viewer is using. Here’s a great article explaining the history of the User Agent. There are ways toĭevelop your web site to progressively enhance itself based on theĪvailability of features rather than by targeting specific browsers. Regardless of which browser or device they’re using. The Web is meant to be accessible to everyone, Serving different Web pages or services to different browsers is Often, web developers will UA sniffing for browser detection. I should point out, that this isn’t a radical departure from what Microsoft did with IE 11, which on Windows 8 reads: Mozilla/5.0 (Windows NT 6.3 Trident/7.0 rv:11.0) like Gecko, as explained in this post. You’ll also notice that the entire string ends with “Edge/12.0″, which Chrome does not. Neowin recently reported that Microsoft’s new browser for Windows 10, Spartan, uses the Chrome UA string, “Mozilla/5.0 (Windows NT 10.0 WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/.71 Safari/537.36 Edge/12.0″.
0 kommentar(er)
