Compatibility Master Table

Hell is other browsers — Sartre

My Compatibility Tables are by far the most popular resource on this site. Here you find the master table that contains links to the individual tables.

This is a general overview table; a Yes here does not mean a browser supports every tiny detail of the specification correctly. Instead, it means that it supports a workable subset of the specification. In IE’s case this may mean that it supports its proprietary methods and properties, and that those properties are generally equivalent to the W3C spec.

A “To be tested” means that I haven’t yet tested the specific browser named in the table. Usually the detail table contains data about a previous version, though.

An “Untestable” means that I no longer have that browser available due to browser vendors’ absurd update policies that remove older versions without warning.

When I test new browsers I do not always run all the tests; doing so would cost me about a week of full-time work. Therefore most tables usually lag behind the latest crop of browsers. In general, when a new test round starts I test the table that’s most behind and work my way up to the more recently updated tables.

Load the update dates of the individual tables (may take a little while).

Selector	IE 5.5	IE 6	IE 7	IE8 as IE7	IE8 as IE8	FF 2	FF 3.0	FF 3.5	Saf 3.0 Win	Saf 3.1 Win	Saf 4.0 Win	Chrome 1	Chrome 2	Opera 9.62	Opera 10b	Konqueror 3.5.7
CSS 2	Incorrect		Incomplete		Yes	Yes		To be tested	Yes		To be tested	Yes		Yes	To be tested	Yes
CSS 2	CSS 2 has become the baseline of CSS support; without it a browser is decidedly backward.
CSS 3	Minimal				Incomplete	Almost		To be tested	Incomplete	Almost	To be tested	Almost		Almost	To be tested	Almost
CSS 3	The compatibility information here is about the CSS3 modules I test. It is not necessarily valid for the browsers’ entire CSS3 support.
DOM Core Node manipulation	Yes					Yes		To be tested	Yes		To be tested	Yes		Yes	To be tested	Yes
DOM Core Node manipulation	The W3C DOM Core module defines how to access, read and manipulate an XML document. Well-formed HTML documents are XML documents, so these methods and properties can be used to completely rewrite any HTML page, if you so wish. Here you find details on how to find elements, how to create new ones, how to read out node information and how to change the structure of the document.
DOM HTML HTML tag manipulation	Yes					Yes		To be tested	Yes			Yes		Yes		Yes
DOM HTML HTML tag manipulation	Though HTML documents are XML documents, they have a number of special features that the average XML document doesn't have. The W3C DOM HTML module defines these special cases and how to deal with them. Here you find details on getting and setting properties of HTML elements, such as `className` or `id`. The `innerHTML` property is of prime importance to any DOM script.
DOM CSS Stylesheet manipulation	Yes			To be tested		Yes		To be tested	Yes		To be tested	Yes	To be tested	Yes	To be tested	Yes
DOM CSS Stylesheet manipulation	Style sheets are part of the document, too (sort of). The W3C DOM CSS module gives access to style sheets and allows you to change a style sheet. This module contains some browser incompatibilities, but they are of the cute kind. W3C and Microsoft define some different methods and arrays, but some simple object detection allows you to evade these problems.
DOM Traversal Get element nodes; make sure text and comment nodes don’t mess up your scripts.	No					No		Yes	No	Untestable	Yes	Untestable	Yes	Yes		To be tested
	Useful properties that should have been in the DOM in the first place.
DOM Events	Yes			To be tested		Yes		To be tested	Yes		To be tested	Yes	To be tested	Yes	To be tested	Almost
DOM Events	Event support in all browsers. Konqueror lacks support for some common events.
CSS Object Model View Element dimensions, mouse coordinates, and miscellaneous	Almost					Yes		To be tested	Yes		To be tested	Yes		Yes	To be tested	Yes
	This specification contains several age-old properties that all browser support but that never have made it to a W3C specification yet.
HTML5 HTML5 features	No			Yes		No		To be tested	No	Untestable	Yes	Untestable	No	No		To be tested
HTML5 HTML5 features	The compatibility information above is only for the HTML5 features I tested; they do not necessarily say anything about the browsers’ overall HTML5 support. The number of tests will slowly expand.
Selector	IE 5.5	IE 6	IE 7	IE8 as IE7	IE8 as IE8	FF 2	FF 3.0	FF 3.5	Saf 3.0 Win	Saf 3.1 Win	Saf 4.0 Win	Chrome 1	Chrome 2	Opera 9.62	Opera 10b	Konqueror 3.5.7

Mobile tables

Touch events. Created in February 2010.
Widths, about media queries, window.innerWidth, screen.width, documentElement.offsetWidth, and other extremely complicated stuff. Will have to include definitions and tests of the resize and zoom events. Draft table; use with care.
CSS. Created in 2009.
Widget object for in W3C Widgets. Created in 2009.
DOM Core. Created in 2009.

Other resources

In addition to the tables mentioned above I created the following resources that are unfortunately out-of-date. Use with care:

DOM Event properties (mouse buttons, keys, targets etc.) Severely outdated.
Range. A Range is an arbitrary part of an HTML document. Typically you use this interface to mess with a text the user has selected. Severe incompatibility problems.
execCommand. This method allows you to change DOM nodes in ways useful in a rich text editor. Originally a Microsoft proprietary method it has meanwhile been adopted by all other browsers.

These compatibility tables are sponsored by