Compatibility mode

Last updated July 06, 2024

A compatibility mode is a software mechanism in which a software either emulates an older version of software, or mimics another operating system in order to allow older or incompatible software or files to remain compatible with the computer's newer hardware or software. Examples of the software using the mode are operating systems and Internet Explorer.

Operating systems

A compatibility mode in an operating system is a software mechanism in which a computer's operating system emulates an older processor, operating system, and/or hardware platform in order to allow older software to remain compatible with the computer's newer hardware or software.

This differs from a full-fledged emulator in that an emulator typically creates a virtual hardware architecture on the host system, rather than simply translating the older system's function calls into calls that the host system can understand.

Examples include Classic Mode in Mac OS X and compatibility mode in Microsoft Windows, which both allow applications designed for older versions of the operating system to run. Other examples include Wine to run Windows programs on Linux / OS X and Mono to run .NET programs on various Unix-like systems.

Internet Explorer

"Compatibility View" is a compatibility mode feature of the web browser Internet Explorer in version 8 and later. When active, Compatibility View forces IE to display the webpage in Quirks mode as if the page were being viewed in IE7.^[1]^[2] When compatibility view is not activated, IE is said to be running in native mode. In IE11, a user can turn on compatibility mode for a web site by clicking the Gears icon and clicking Compatibility View Settings.

IE8+

Internet Explorer 8 was promoted by Microsoft as having stricter adherence to W3C described web standards than Internet Explorer 7. As a result, as in every IE version before it, some percentage of web pages coded to the behavior of the older versions would break in IE8. This would have been a repetition of the situation with IE7 which, while having fixed bugs from IE6, broke pages that used the IE6-specific hacks to work around its non-compliance. This was especially a problem for offline HTML documents, which may not be updatable (e.g. stored on a read-only medium, such as a CD-ROM or DVD-ROM).

To avoid this situation, IE8 implemented a form of version targeting whereby a page could be authored to a specific version of a browser using the X-UA-Compatible declaration either as a meta element or in the HTTP headers.^[3]

In order to maintain backwards compatibility, sites can opt into IE7-like handling of content by inserting a specially created meta element into the web page that triggers compatibility mode in the browser, using:^[4]

<metahttp-equiv="X-UA-Compatible"content="IE=EmulateIE7"/>

A newer version of the browser than the page was coded for would emulate the behavior of the older version, so that the assumptions the page made about the browser's behavior hold true.

Microsoft proposed that a page with a doctype that triggers standards mode (or almost standards mode) in IE7 would, by default, trigger IE7-like behavior, called "standards mode" (now called "strict mode") in IE8 and future versions of IE. The new features of IE8 are enabled to trigger what Microsoft called the "IE8 standards mode" (now called "standards mode"). Doctypes that trigger quirks mode in IE7 will continue to do so in IE8.

Peter Bright of Ars Technica claimed that the idea of using a meta tag to pick a specific rendering mode fundamentally misses the point of standards-based development but positioned the issue as one of idealism versus pragmatism in web development, noting that not all of the Web is maintained, and that "demanding that web developers update sites to ensure they continue to work properly in any future browser version is probably too much to ask."^[5]

The result for IE 8 Beta 1 was that it could render three modes: "Quirks," "Strict," and "Standard." When there is an old DOCTYPE or when there is no DOCTYPE, IE renders it like IE5 would (quirks mode). When a special meta element or its corresponding HTTP header is included in a web page, IE8 will render that page like IE7 would (strict mode). Otherwise, IE8 renders pages with its own engine (standard mode). Users can switch between the three modes with a few clicks.^[6] The release of Internet Explorer 8 Beta 1 revealed that many web sites do not work in this new standards mode.

Microsoft maintains a list of websites that have been reported to have problems in IE8's standards mode, known as the compatibility view list. When a user enables this list IE8 will render the websites in the list using its compatibility view mode.^[7] The list is occasionally updated to add newly reported problematic websites, as well as to remove websites whose owners have requested removal. The Internet Explorer team also tests the websites on the list for compatibility issues and removes those where none are found.^[8]

Related Research Articles

Internet Explorer is a retired series of graphical web browsers developed by Microsoft that were used in the Windows line of operating systems. While IE has been discontinued on most Windows editions, it remains supported on certain editions of Windows, such as Windows 10 LTSB/LTSC. Starting in 1995, it was first released as part of the add-on package Plus! for Windows 95 that year. Later versions were available as free downloads or in-service packs and included in the original equipment manufacturer (OEM) service releases of Windows 95 and later versions of Windows. Microsoft spent over US$100 million per year on Internet Explorer in the late 1990s, with over 1,000 people involved in the project by 1999. New feature development for the browser was discontinued in 2016 and ended support on June 15, 2022 for Windows 10 Semi-Annual Channel (SAC), in favor of its successor, Microsoft Edge.

Gecko is a browser engine developed by Mozilla. It is used in the Firefox browser, the Thunderbird email client, and many other projects.

Trident is a proprietary browser engine for the Microsoft Windows version of Internet Explorer, developed by Microsoft.

DOM Events are a signal that something has occurred, or is occurring, and can be triggered by user interactions or by the browser. Client-side scripting languages like JavaScript, JScript, VBScript, and Java can register various event handlers or listeners on the element nodes inside a DOM tree, such as in HTML, XHTML, XUL, and SVG documents.

Windows Internet Explorer 7 (IE7) is a web browser for Windows. It was released by Microsoft on October 18, 2006. It is part of a long line of versions of Internet Explorer and was the first major update to the browser. It does not support earlier versions of Windows.

<span class="mw-page-title-main">Acid2</span> Online HTML rendering test

Acid2 is a webpage that test web browsers' functionality in displaying aspects of HTML markup, CSS 2.1 styling, PNG images, and data URIs. The test page was released on 13 April 2005 by the Web Standards Project. The Acid2 test page will be displayed correctly in any application that follows the World Wide Web Consortium and Internet Engineering Task Force specifications for these technologies. These specifications are known as web standards because they describe how technologies used on the web are expected to function.

<span class="mw-page-title-main">History of Internet Explorer</span>

Microsoft developed 11 versions of Internet Explorer for Windows from 1995 to 2013. Microsoft also developed Internet Explorer for Mac, Internet Explorer for UNIX, and Internet Explorer Mobile respectively for Apple Macintosh, Unix, and mobile devices; the first two are discontinued but the latter runs on Windows CE, Windows Mobile, and Windows Phone.

Microsoft Internet Explorer 6 (IE6) is a web browser developed by Microsoft for Windows operating systems. Released on August 24, 2001, it is the sixth, and by now discontinued, version of Internet Explorer and the successor to Internet Explorer 5. It does not support earlier versions.

Microsoft Internet Explorer 5 (IE5) is the fifth, and by now, discontinued, version of the Internet Explorer graphical web browser, the successor to Internet Explorer 4 and one of the main participants of the first browser war. Its distribution methods and Windows integration were involved in the United States v. Microsoft Corp. case. Launched on March 18, 1999. Although Internet Explorer 5 ran only on Windows, its siblings Internet Explorer for Mac 5 and Internet Explorer for UNIX 5 supported Mac OS X, Solaris and HP-UX.

In computing, quirks mode is an approach used by web browsers to maintain backward compatibility with web pages designed for old web browsers, instead of strictly complying with web standards in standards mode. This behavior has since been codified, so what was previously standards mode is now referred to as simply no quirks mode.

An HTML Application (HTA) is a Microsoft Windows program whose source code consists of HTML, Dynamic HTML, and one or more scripting languages supported by Internet Explorer, such as VBScript or JScript. The HTML is used to generate the user interface, and the scripting language is used for the program logic. An HTA executes without the constraints of the internet browser security model; in fact, it executes as a "fully trusted" application.

Windows Internet Explorer 8 (IE8) is a web browser for Windows. It was released by Microsoft on March 19, 2009.

Conditional comments are conditional statements interpreted by Microsoft Internet Explorer versions 5 through 9 in HTML source code. They can be used to provide and hide code to and from these versions of Internet Explorer. Conditional comments are not supported in Internet Explorer 10 and 11.

The Acid3 test is a web test page from the Web Standards Project that checks a web browser's compliance with elements of various web standards, particularly the Document Object Model (DOM) and JavaScript.

Extensible HyperText Markup Language (XHTML) is part of the family of XML markup languages which mirrors or extends versions of the widely used HyperText Markup Language (HTML), the language in which Web pages are formulated.

In computing, version targeting is a technique that allows a group of users to use some advanced software features that were introduced in a particular software version while allowing users accustomed to the prior versions to still use the same software as if the new features were never added to the software. It is a way to ensure backward compatibility when new software features would otherwise break it.

Internet Explorer is a series of graphical web browsers developed by Microsoft and included as part of the Microsoft Windows line of operating systems, starting in 1995.

<span class="mw-page-title-main">Google Chrome Frame</span> Plug-in designed for Internet Explorer based on the open-source Chromium project

Google Chrome Frame was a plug-in designed for Internet Explorer based on the open-source Chromium project, first announced on September 22, 2009. It went stable in September 2010, on the first birthday of the project. It was discontinued on February 25, 2014 and is no longer supported.

<span class="mw-page-title-main">CSS box model</span> Model used for styling websites

In web development, the CSS box model refers to how HTML elements are modeled in browser engines and how the dimensions of those HTML elements are derived from CSS properties. It is a fundamental concept for the composition of HTML webpages. The guidelines of the box model are described by web standards World Wide Web Consortium (W3C) specifically the CSS Working Group. For much of the late-1990s and early 2000s there had been non-standard compliant implementations of the box model in mainstream browsers. With the advent of CSS2 in 1998, which introduced the box-sizing property, the problem had mostly been resolved.

EdgeHTML is a proprietary browser engine from Microsoft that was formerly used in Microsoft Edge, which debuted in 2015 as part of Windows 10.

References

↑ "2.1.2.5 Compatibility View". [MS-IEDOCO]: Internet Explorer Standards Support Documentation Overview. Microsoft. 2015.
↑ "Fix site display problems with Compatibility View". Microsoft Windows: How To. Microsoft. Retrieved 29 July 2015.
↑ Aaron Gustafson (January 21, 2008). "Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8" . Retrieved 2007-03-22.
↑ MSDN "What's New in Internet Explorer 8" Archived 2008-04-18 at the Wayback Machine .
↑ Peter Bright (January 24, 2008). "Wisdom and folly: IE8's super standards mode cuts both ways". Ars Technica . Retrieved 2008-03-21.
↑ Mary Jo Foley. "IE 8 to feature WebSlices, Activities". CNet Blogs. Archived from the original on March 6, 2008. Retrieved 2007-03-05.
↑ "Understanding the Compatibility View List". MSDN. Microsoft. Retrieved 2009-09-06.
↑ Scott Dickens (July 21, 2009). "Update on the Compatibility View List in Internet Explorer 8". IEBlog. Microsoft. Retrieved 2009-09-06.

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.

[1] "2.1.2.5 Compatibility View". [MS-IEDOCO]: Internet Explorer Standards Support Documentation Overview. Microsoft. 2015.

[2] "Fix site display problems with Compatibility View". Microsoft Windows: How To. Microsoft. Retrieved 29 July 2015.

[beyonddoctype-3] Aaron Gustafson (January 21, 2008). "Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8" . Retrieved 2007-03-22.

[msdnie8new-4] MSDN "What's New in Internet Explorer 8" Archived 2008-04-18 at the Wayback Machine .

[Wisdom-5] Peter Bright (January 24, 2008). "Wisdom and folly: IE8's super standards mode cuts both ways". Ars Technica . Retrieved 2008-03-21.

[mjfoley-6] Mary Jo Foley. "IE 8 to feature WebSlices, Activities". CNet Blogs. Archived from the original on March 6, 2008. Retrieved 2007-03-05.

[msdn_compat_view-7] "Understanding the Compatibility View List". MSDN. Microsoft. Retrieved 2009-09-06.

[ieblog_cvl_update-8] Scott Dickens (July 21, 2009). "Update on the Compatibility View List in Internet Explorer 8". IEBlog. Microsoft. Retrieved 2009-09-06.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]