In my experience across the Enterprise Portal area many of the scenarios that I deal with on a daily basis revolve around browser bases issues or scenarios that in some way, shape or form associate to the Web Browser Platform itself. From a high level perspective we think as a Web Browser Platform as a simple conduit through which we can gain access to and interact with Web Based Resources and this is indeed true. However we need to remember that with each Web Browser Platform comes a set of different parameter and property settings which need to be maintained in order to support optimal performance. In reference to “performance” here I do not mean the speed of the browser 😆 but rather the means in which it functions i.e. the rendering of the browser & subsequent display presented to end users.
Quirks, Standards, Edge..
I would like to stress the importance at looking over browser configurations and the various modes from the most simple standpoint possible. With browser related scenarios a simple issue can quickly become a complex scenario especially taking all the various parameters into account within a troubleshooting scenario.
In the interest of simplicity we can look at things as below (in a modern browser environment):
- Quirks: displays webpages as if users view them with older versions of the browsers.
- Standards: HTML 5 engine, new features are only supported in this mode.
Is there a way to “Force” all Pages to be displayed within Edge Mode?
If you want to achieve from a functional aspect “forcing” all Pages to run in browser document mode EDGE essentially here we are referring to standards.
To achieve this you would need to use the Standards Ajax Framework Page which is available from NW7.31 SP14 and 7.4 SP9. This is basically an Ajax framework page that runs in Standards Mode.
However this does not cover applications for example if you are using older HTMLB style applications these require Quirks Mode.
Attempting to run old applications that require Quirks mode, will need to be run in a new headerless window or new window in order to see the content.
Ajax Standards Mode Framework Page
Reviewing Different Modes
Remember we need to look at Internet Explorer as a Web Browser Platform with core fundamental underlying parameters which determine the way it functions and how it operates in association to an Enterprise Portal environment.
From a purely navigation approach here we are dealing with two key modes which are that of Browser & Document Mode.
What is the Browser Mode all about?
In short the browser mode is a user agent string sent to the server (which affects the User Agent only).
- When compatibility mode is selected the the User Agent is set to the oldest supported setting for the current browser.
- Tools > Compatibility View > F12 > Navigation > Navigation.UserAgent
- IE10, IE10 Compatibility View, IE9, IE8, IE7.
The User Agent is essentially a string (textual) which identifies the Browser & OS to for the Web Server. To provide insight with a working example if we take IE5 Quirks which is the oldest document mode as the baseline. This means Internet Explorer is telling the server its browser mode. According to the browsers mode the server then decides which resources CSS/JS should be sent back to the Browser.
So What is the Document Mode all about?
Document Mode: Determines how the browser (IE) renders the page.
- Essentially tells browsers how it wants it to be rendered.
- Browser decides which rendering engine should be used.
From a high level perspective let us remember that Document Mode determines how Internet Explorer is rendered.Quirks Mode displays the webpages as if they are within older IE versions while Standards Mode follows the HTML5 Engine with new features supported. The Quirks Mode syntax is different from the Standards Mode syntax.