(For 32-bit windows, it is HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION ) HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION\nlclient.exe You can also experiment with other values like 9000 if you don’t even target IE8. (For 32-bit windows, it is HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION) Meta http-equiv="X-UA-Compatible" content="IE=Edge"/Īnother option is to create a registry key on all workstations running the console: HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION\nlclient.exe You can also use IE=8, depending on your version. It does not work for delivery previews since they are not delivered over HTTP by the Adobe Campaign server. It is an embedded IE control that contains customized HTML. The HTTP X-UA-Compatible header does not apply, and the embedded IE forces compatibility mode.įor such cases, these are the following workarounds:Īdd the following meta tag in your delivery’s HEAD nodes. (X-UA-Compatible: IE=Edge), ensure that this block is not present.
How to stop Internet Explorer from rendering in compatibility mode? ResolutionĮdit /tomcat-7/conf/web.xml of the instance and add the following lines: filterį/filter- classĪdd the lines, but set the desired value inside the added element. How to avoid Internet Explorer rendering in compatibility mode? DescriptionĪdobe Campaign Classic (version 6.1 build 8021 or later)
0 kommentar(er)
