Internet Explorer Compatibility View

-

The newer Internet Explorer comes with the F12 Developer Tools wherein you find the Browser Mode and the Document Mode.

Difference between the Browser Mode and the Document Mode

Document Mode is something that the web server can control. By specifying the HTTP header, the HTML meta-tags, or the DocType declaration, the Document Mode changes accordingly. See my earlier article.

However, the Browser Mode cannot be changed by the server.

What really happens when IE Compatibility View is activated?

when IE Compatibility View is activated, the HTTP user-agent header is changed to that of IE7.

The user-agent sent by the browsers follows:

IE Browser Mode User-Agent
IE10 Mozilla/5.0 (compatible; MSIE 10.0;
Windows NT 6.1; Trident/6.0)
IE9 Mozilla/5.0 (compatible; MSIE 9.0;
Windows NT 6.1; Trident/5.0)
IE8 Mozilla/4.0 (compatible; MSIE 8.0;
Windows NT 6.1; Trident/4.0)
IE7 Mozilla/4.0 (compatible; MSIE 7.0;
Windows NT 6.1)
IE10 WinPhone Mozilla/5.0 (compatible; MSIE 10.0;
Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch)
IE Compatible View Mozilla/4.0 (compatible; MSIE 7.0;
Windows NT 6.1; Trident/6.0)

Note:

  1. Operating System differences:
    1. Windows 8 uses NT 6.2
    2. Windows 7 uses NT 6.1
    3. Windows Vista uses NT 6.0
  2. Layout Engine differences: regardless of Browser Mode in use,
    1. IE 10 browser uses Trident 6.0
    2. IE 9 browser uses Trident 5.0
    3. IE 8 browser uses Trident 4.0

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

Apache Web Server Troubleshooting

-
How to troubleshoot Apache Web Server? A few standard commands to know by hard: To confirm the modules that are or will be loaded in Apache: apachectl –M [-f <conf filename>] To check the virtual host load pattern: apachectl –S [-f <conf filename>] To test a httpd.conf file: apachectl –t [-f <conf filename>] To maintain the http server: apachectl start|stop|restart To start with a specified configuration file: apachectl –f <conf filename> Create a minimalist httpd.conf. Something like: Listen 80 ServerName myserver.com:80 ServerAdmin admin@myserver.com #ServerRoot " . " ServerRoot " /usr/local/apache2 " User nobody Group nobody #DocumentRoot " ..\wwwroot " DocumentRoot " /home/data/html " ErrorLog " logs/basic_apache.log " LogLevel debug #LoadModule log_config_module modules/mod_log_config.dll LoadModule log_config_module modules/mod_log_config.so <IfModule log_config_module> LogFormat " %h %l
Read more