It sounds as though you’re not in a modern document mode. Internet Explorer 11 shows the SVG just fine when you’re in Standards Mode. Make sure that if you have an x-ua-compatible meta tag, you have it set to Edge, rather than an earlier mode. <meta http-equiv=”X-UA-Compatible” content=”IE=edge”> You can determine your document mode by … Read more
You can explicitly detect IE11 with the following check (using feature detection): if (Object.hasOwnProperty.call(window, “ActiveXObject”) && !window.ActiveXObject) { // is IE11 } Explanation: All versions of IE (except really old ones) have window.ActiveXObject property present. IE11, however hides this property from DOM and that property is now undefined. But the property itself is present within … Read more
I had the same issue, I solved it by adding this meta tag as the FIRST tag in <head>: <meta http-equiv=”X-UA-Compatible” content=”IE=edge”> Also, according to the official documentation, check the following: For Internet Explorer: you don’t serve files with no-store option in Cache-control header (Ref: #6454); For Internet Explorer and HTTPS: you don’t serve files … Read more
IE 11 does not like a domain value in the cookie. Leave it empty. Wrong for IE 11: Set-Cookie: kohanasession=foobar; expires=Tue, 09-Apr-2016 01:01:01 GMT; path=/; domain=tc.mk; httponly Correct for IE 11: Set-Cookie: kohanasession=foobar; expires=Tue, 09-Apr-2016 01:01:01 GMT; path=/; httponly
to avoid this funny behavior, you may reset the flex-shrink property. This looks like a bug, despite what Microsoft says: <‘flex-shrink’> Sets the flex shrink factor or negative flexibility for the flex item. The flex shrink factor determines how much a flex item will shrink relative to the other items in the flex container. If … Read more
You saw it right. As per the documentation in the Required Configuration section of InternetExplorerDriver it is clearly mentioned: For IE 11 only, you will need to set a registry entry on the target computer so that the driver can maintain a connection to the instance of Internet Explorer it creates. For 32-bit Windows installations, … Read more
[UPDATE] The original question, and the answer below applied specifically to the IE11 preview releases. The final release version of IE11 does in fact provide the ability to switch browser modes from the Emulation tab in the dev tools: Having said that, the advice I’ve given here (and elsewhere) to avoid using compatibility modes for … Read more
Turns out this is a problem in the base version of IE11 (11.0.9600.16428) for Windows 7 SP1. After installing a patch to update to 11.0.9600.16476 (update version 11.0.2 – KB2898785) the issue gets resolved. Links to other versions of Windows (32-bit etc.) can be found at the bottom of the patch download page.
If you look at the ECMAScript 6 compatibility table, you’ll see that template literals are not supported by IE11. The “use strict”; statement doesn’t really change anything, because before it is determined whether a code is in strict mode, it has to be parsed first, but it can’t be parsed, because you’re using syntax that the … Read more
In the light of the evolving thread, I have updated the below: IE 6 * html .ie6 {property:value;} or .ie6 { _property:value;} IE 7 *+html .ie7 {property:value;} or *:first-child+html .ie7 {property:value;} IE 6 and 7 @media screen\9 { .ie67 {property:value;} } or .ie67 { *property:value;} or .ie67 { #property:value;} IE 6, 7 and 8 @media … Read more