| Summary | This document describes various mitigation techniques and configurations to get the best rendering in Internet Explorer. It is especially powerful when embedded in Adobe Campaign Console. The main idea is to avoid IE rendering in compatibility mode (IE 7 look). |
| Digital Marketing Solution(s) |
Adobe Campaign v6.1 from build 8021 Adobe Campaign v6.11 Adobe Campaign v7 |
| Audience | Technical administrators |
In the past (6.1 build < 8021), the server never explicitly sent user agent compatibility mode headers (X-UA-Compatible) to the web clients. Some pages contained the following meta tag but it did not always work due to tedious IE heuristics, mostly using the console.
<meta http-equiv="X-UA-Compatible" content="IE=Edge"/>
X-UA-Compatible: IE=edge
This header effectively makes the console and IE render using the latest available algorithms. The update has solved all reported compatibility issues.
If this new behavior is not wanted, administrators can change the web server configuration as follows:
- To restore the old behavior (no X-UA-Compatible header set by the server), edit /tomcat-7/conf/web.xml of the instance, and add the following lines:
<filter>
<filter-name>HttpHeaderFilter</filter-name>
<filter-class>com.neolane.jssp.HttpHeaderFilter</filter-class>
+ <init-param>
+ <param-name>X-UA-Compatible</param-name>
+ <param-value></param-value>
+ </init-param>
</filter>
- To set a different value, also add the lines, but set the desired value inside the added element.
- To restore the default new behavior (X-UA-Compatible: IE=Edge), ensure that this block is not present
Observação:
In any event, if you feel the need to perform such changes on any instance, contact the R&D department. It can have complex impacts on all IE clients.
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 into which contains the customized HTML. The http X-UA-Compatible header does not apply, and the embedded IE forces compatibility mode.
For those cases, there are the following work-arounds:
- Add the following meta tag in your delivery's <HEAD> nodes. You can also use IE=8 depending on your version.
<meta http-equiv="X-UA-Compatible" content="IE=Edge"/>
- Another 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 (For 32-bit windows, it is HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION ) Type: DWORD Value: 8000 (decimal)
As publicações do Twitter™ e do Facebook não são cobertas pelos termos do Creative Commons.