none
Document modes deprecation RRS feed

  • Question

  • Hello,

    I am trying to understand the full extent of the impact of the deprecation of Document modes based on this post.

    http://msdn.microsoft.com/en-us/library/ie/dn384051%28v=vs.85%29.aspx

    Our product leverages quirks mode in certain areas. With these deprecations does that mean that with IE12 those components that remain in Quirks Mode will simply not work, or they will be rendered in correctly?

    I am trying to get an understanding of the potential scope of the issue in order to allow time to resolve the issue before the issue is forced.

    Thank you

    Thursday, December 19, 2013 2:48 PM

Answers

  • Hi,

    IE10 introduced IE10 quirks mode......that replaced IE5 quirks mode of previous versions of IE...

    If your legacy documents do not have a valid Document type declaration, then IE10 and 11 will treat them like a valid Near Standards document (document.documentMode==Edge, document.compatMode==backCompat) whereas IE9 and earlier will continue to use Quirks mode redering (documentMode==5, document.compatMode==backCompat)

    IE8 and higher treat all web documents with a valid document type declaration as a 'Standards' compliant document (document.documentMode==8,9,10 or 11 or 12, and document.compatMode==CSS1Compat)

    vml is no longer supported in IE9 documentModes and higher.

    xml dataislands and addBehavior is not longer supported in documentModes and higher.

    the x-ua meta values were meant to provide a temporary means of providing backwards compatibility to legacy web documents only.

    There are various shims and polyfills like jQuery, excanvas that allow you to migrate to standards based markup and scripting while still maintaining back compatibility for parts of your network that are still using older versions of IE or other web browsers.


    Rob^_^

    Friday, December 20, 2013 1:41 AM

All replies

  • Hi,

    IE10 introduced IE10 quirks mode......that replaced IE5 quirks mode of previous versions of IE...

    If your legacy documents do not have a valid Document type declaration, then IE10 and 11 will treat them like a valid Near Standards document (document.documentMode==Edge, document.compatMode==backCompat) whereas IE9 and earlier will continue to use Quirks mode redering (documentMode==5, document.compatMode==backCompat)

    IE8 and higher treat all web documents with a valid document type declaration as a 'Standards' compliant document (document.documentMode==8,9,10 or 11 or 12, and document.compatMode==CSS1Compat)

    vml is no longer supported in IE9 documentModes and higher.

    xml dataislands and addBehavior is not longer supported in documentModes and higher.

    the x-ua meta values were meant to provide a temporary means of providing backwards compatibility to legacy web documents only.

    There are various shims and polyfills like jQuery, excanvas that allow you to migrate to standards based markup and scripting while still maintaining back compatibility for parts of your network that are still using older versions of IE or other web browsers.


    Rob^_^

    Friday, December 20, 2013 1:41 AM
  • Hi Rob,

    Thank you very much. I am going to review this with some folks here and might be back with more questions

    Monday, December 30, 2013 12:55 PM