IE Edge Mode

If you’re using Internet Explorer and run into weird problems accessing OpenText Content Suite or Extended ECM, usually after a major upgrade, one thing to check is “emulation mode” and specifically is Internet Explorer running in “Edge” mode. OpenText upgraded to a much more modern javascript framework in Content Suite 16.2.5 so customviews that worked in previous releases of the Content Suite platform (e.g. Content Suite 10.5) may no longer work with Internet Explorer.

This problem affects Internet Explorer 11 or earlier (this problem doesn’t affect other browsers such as Edge, Chrome, and Firefox). Core Content Suite applications seem to work fine; however, custom applications that have their own html headers such as display views and custom views may not work as expected.

To check whether your copy of Internet Explorer is running in “Edge” mode, log-in to your Content Suite platform, right-click the page and select “Inspect” and then check the mode in the far right of the console; see the screenshot below.

Screenshot IE Edge mode

If your IE version is the same as the selected mode (in the screenshot it’s set to 11) then IE is running in Edge mode then emulation mode is not the solution. If your IE version is greater than the selected mode, however, then you’re not running in Edge mode. In this case, force IE to operate in Edge mode may be the solution to your problem.

Therefore, best practice is to force IE to operate in Edge mode. To do so, add the following to your HTML source (such as a form’s customview)

<meta http-equiv=”X-UA-Compatible” content=”IE=Edge” />

This tag forces IE to use Edge mode.

Happy coding!