Will IE11 support moz-prefixed functionality? Of course, that’s usually not the case, especially when it comes to vendor-prefixed functionality. Gecko- and WebKit-based browsers both are considered to have better standards support than Internet Explorer (generally well-deserved prior to IE10), so tricking servers into identifying IE11 as a Gecko-based browser could mean that the browser can handle the same content (JavaScript, CSS) as Firefox.
By adding “like Gecko” at the end, it is self-selecting into the category of Gecko-based browsers (step 6). In short, by removing “MSIE” in favor of “IE”, the browser is forcing itself to not be identified as Internet Explorer (step 1). So if the Internet Explorer 11 user-agent string is the final one, it causes some interesting logic to happen in this case. Else if “Gecko” is present, it’s a Gecko-based browser.
Else if “WebKit” is present, it’s a WebKit-based browser. Else if “Safari” is present, it’s Safari. Else if “Chrome” is present, it’s Chrome. Else if “Firefox” is present, it’s Firefox. If “MSIE” is present, it’s Internet Explorer. Simple browser type detection based on user-agent string meant you would need to look for certain tokens in order: Not long ago, WebKit overtook Gecko as the embeddable webview of choice, and so many started looking for “Firefox” in the user-agent string to specifically identify Firefox.Ĭhrome came along and wanted to be identified as Safari, so it pretty much copied the Safari user-agent string and added a “Chrome” identifier. That approach fell apart when Safari decided to add “like Gecko” into the middle of its user-agent string. When Gecko was the embedded webview of choice, many simply looked for “Gecko” in the user-agent string to determine if it was a Gecko-powered browser (and therefore likely to behave as Firefox). If present, the browser is Internet Explorer. In the past, it was easy to identify Internet Explorer by searching for the string “MSIE” in the user-agent string. 
#Internet explorer for mac 11.0 windows#
Mozilla/5.0 (compatible MSIE 10.0 Windows NT 6.1 Trident/6.0)
0 kommentar(er)
