A URL to an Aurena page, launched from a classic-client Custom Menu action, fails to load properly inside IEE's own embedded browser view — but the exact same URL opens perfectly fine in a genuine external browser like Edge or Chrome, even though Edge/Chrome is set as the OS default browser. Why does IEE behave differently from the actual configured default browser?

All FAQ questions / Platform, Aurena, and customization

Answer

IEE's embedded web-browser functionality is built on the older Internet Explorer rendering engine internally, regardless of which browser is actually configured as the Windows default — so a URL that would behave differently or fail specifically under classic Internet Explorer's rendering behaves the same way inside IEE, even if IE itself hasn't been the system default browser in years. If a specific URL/page is known to have issues in Internet Explorer specifically but works fine in Chrome or Edge, expect that same broken behavior to show up when it's opened from inside IEE, since IEE's embedded view uses IE's engine rather than whatever browser is set as the OS default.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions