The current embedded browser within Millennium applications is the Microsoft web browser control. There are a few key points to know about this embedded browser:
The first point above is important because it will be the determining factor for what document modes are available within the embedded web browser control. If the standalone version of Internet Explorer is IE11, then the embedded browser can render using the IE11 document mode. However, as called out in the third point above, the default behavior for the embedded web browser is to utilize document mode 7 (IE7 compatibility mode).
In order to get the embedded web browser to render using a newer document mode, the Compatibility Meta Tag (X-UA-COMPATIBLE) can be added to the web application to utilize the latest browser engine available. The Microsoft Controlling WebBrowser Control Compatibility blog post provides a great writeup of this information and how that meta tag can be leveraged. The setting of ‘edge’ (not to be confused with Microsoft Edge) will render our framework using the latest document mode available from the standalone Internet Explorer browser (currently IE11).
One major caveat of the embedded web browser control is that the userAgent string will always show up as MSIE7. This userAgent string is how many web developers attempt to determine what browser is being utilized. However, this is not the recommended way of determining what browser in use. This Mozilla article provides alternatives to using the userAgent string. There are registry keys that allow for overriding this and forcing the userAgent string to show a newer value, but these cannot be utilized for Millennium applications as there is a mixture of multiple web applications used under the same parent application.
- Yixuan (Cerner)