HTML Compatability Modes

As a web-developer, I find it unfortunately necessary to force a browser(s) to conform to my preferred platform.  That being said, i have not been able (as of this posting) to find a aggregate knowledge base of all the available Meta values for the "X-UA-Compatible" header entry.  So below you will find my currently identified valid values.

Syntax:
<meta http-equiv="X-UA-Compatible" content="<value>"> Possible Values for <value>, by Browser:
  • Internet Explorer = IE
    • IE=5
      • Quirks Mode; pretty much anything less than IE 7
    • IE=7
      • IE 7 Mode
    • IE=8
      • IE 8 Mode
    • IE=9
      • IE 9 Mode
    • IE=10
      • IE 10 Mode
    • IE=11
      • IE 11 Mode
    • IE=edge
      • Highest supported document mode of the browser
    • Quirks Emulate Values (If a valid <!DOCTYPE> declaration is present)
      • IE=EmulateIE7
        • IE 7 Mode; otherwise, Quirks Mode (equivalent to IE=5)
      • IE=EmulateIE8
        • IE 8 Mode; otherwise, Quirks Mode (equivalent to IE=5)
      • IE=EmulateIE9
        • IE 9 Mode; otherwise, Quirks Mode (equivalent to IE=5)
      • IE=EmulateIE10
        • IE 10 Mode; otherwise, Quirks Mode (equivalent to IE=5)
      • IE=EmulateIE11
        • IE 11 Mode; otherwise, Quirks Mode (equivalent to IE=5)
  • Chrome
    • No Support for any values; with Chrome Frame being deprecated and support stopping, no need for knowing this value.
  • FireFox
    • No Support for any values; this was pretty much depracated from being parsed around FF3. May not be factually accurate but sometime between 3 & 4, they dropped the parsing of this Meta Element value structure.
  • Safari
    • No Support for any values; from what I can tell, it was never accepted.
  • Opera
    • No Support for any values
One interesting note about how to perform equivalent operations, is through what one poster (Henri Sivonen) suggested. I will not repost any content, it very well formatted and thought out, to me. He says it point blank how it "should" be.

Comments

Post a Comment

Popular posts from this blog

SysInternals - BgInfo for ALL Users

Image
I have seen various sites that have been pretty good at getting close to the point of getting Background Information created by the tool BgInfo but none of them have actually solved my specific problem. Solutions currently out there include: Placing into the "All Users" folder This did not work for me, as our implementation does not contain an "All Users" folder in the "Users" folder for profiles. Reg-Hacking and HKCU or HKLM entry This is the worst of all the bad choices available.  I am experienced with Registry Editing and I still would not want or find a need to do this. Placing into the "Default" folder This is good going forward but what about those 20+ user profiles that are already logged in.  FYI, if your server has 20+ user account profiles in the "Users" directory you have larger problems than I am willing to assist with in this posting. The solution that worked for me, will be described below in pain-staki
Read more

JSON/AJAX Helpers

Recently, had an implementation where I needed to implement ASP.Net Web API 2 and accompanied it with Javascript/JQuery AJAX communication.  In doing this i found myself making the same pattern calls with some varying value for certain properties for the AJAX data calls.  As such, i ended up building a few helper functions to simply the inclusion of these various minor quirks based on what was needed.  Below  you will find the various forms. 1: /********************************************************************* 2: @type - dataType, such as 'json', 'xml', 'script', 'jsonp' or 'html' 3: @contentType - string value, represents the HTML type of content 4: IE: 'application/json; charset=utf-8' 5: @url - API URL, such as 'api/tasks' should be constrainted to the 6: Web API Controller 7: @success - Function(data, status, xhr) handler, The logic to execute 8: on a 200 res
Read more

Acquiring List of controls - Classic JS

Recently ran into a scenario where I need to use the low-level JavaScript parser, instead of JQuery.  During this venture, I ran across a situation where it would be easier for me to select all the HTML Elements with an ID, assign it to a variable as JSON, and then operate on it from that point. So using my previous short-hand experience with JQuery, I started constructing a similar type of format to be used. *********** JQuery *************** // One line and your done, pretty much var cntrls = $('[id]') // Later on, you simply access the element from the variable var val = cntrls['someID'].value *********** JavaScript *********** // Not so one-liner; put in the DOM.Ready event for JS var cntrlIDs = {} var root = document.getElementById('rootID').querySelectorAll('*'); for (i = 0, n = root.length; i < n; ++i) { var el = root[i]; if (el.id) { cntrlIDs[el.id] = el; } } // Later
Read more