How can we help you?

W3C and WHATWG conflict

W3C and WHATWG have been characterized as both working together on the development of HTML 5,[14] and yet also at cross purposes[30][2] ever since the July 2012 split of the W3C work into milestone-based static standards and WHATWG's into a continually updated "living standard". The relationship has been described as "fragile", even a "rift",[40] and characterized by "squabbling".[2]

In at least one case, namely the permissible content of the <cite></cite> element, the two specifications directly contradict each other (as of July 2018), with the W3C definition being permissive and reflecting traditional use of the element since its introduction,[41] but WHATWG limiting it to a single defined type of content (the title of the work cited).[42] This is actually at odds with WHATWG's stated goals of ensuring backward compatibility[43] and not losing prior functionality.[30]

The "Introduction" section in the WHATWG spec (edited by Ian "Hixie" Hickson) is critical of W3C, e.g "Note: Although we have asked them to stop doing so, the W3C also republishes some parts of this specification as separate documents." In its "History" subsection it portrays W3C as resistant to Hickson's and WHATWG's original HTML 5 plans, then jumping on the bandwagon belatedly (though Hickson was in control of the W3C HTML 5 spec, too). Regardless, it indicates a major philosophical divide between the organizations:[44]

For a number of years, both groups then worked together. In 2011, however, the groups came to the conclusion that they had different goals: the W3C wanted to publish a "finished" version of "HTML5", while the WHATWG wanted to continue working on a Living Standard for HTML, continuously maintaining the specification rather than freezing it in a state with known problems, and adding new features as needed to evolve the platform.

Since then, the WHATWG has been working on this specification (amongst others), and the W3C has been copying fixes made by the WHATWG into their fork of the document (which also has other changes).

The "markets" for the two specifications are largely different. The W3C spec is the one that Web developers most often refer to,[citation needed] while the WHATWG version is used by the software development teams of the browser makers (though a version exists for Web content authors, trimmed of the material only of interest to browser coders[6]). New features are added to HTML and, often experimentally, to browsers long before they appear in a W3C spec, because they arise in the WHATWG one.[40] The technology journal Ars Technica observed that "both groups are likely to continue to exist, and both groups will continue to have broad-based industry backing".[2]

Differences between the two standards

In addition to the contradiction in the <<a href="" title="HTML elements">cite</a>> element mentioned above, other differences between the two standards include at least the following, as of September 2018:

Content or Features Unique to W3C or WHATWG Standard

Site paginationSingle page version[47] (allows global search of contents)
Chapters§5 Microdata[48]

§9 Communication[49]

§10 Web workers[50]

§11 Web storage[51]

Global attributes[52]classid[53]autocapitalizeenterkeyhintinputmodeisitemiditempropitemrefitemscopeitemtypenonce
Chapter Elements of HTML§4.13 Custom elements[54]
Elements<rb></rb>[55]<rtc></rtc>[56] (See compatibility notes below.)

[57] is in section Grouping content.
[58][59]<slot></slot>[60] (See compatibility notes below.)

[61] is in section Sections.
§ <meta>§ Other pragma directives[62], based on deprecated WHATWG procedure[63].
§ Sections§ Sample outlines[64]

§ Exposing outlines to users[65]

Structured dataRecommends RDFa (code examples[66][57][67], separate specs[68][69], no special attributes[52]).Recommends Microdata (code examples[70][71][72][73], spec chapter[48], special attributes[53]).

The following table provides data from the Mozilla Development Network on compatibility with major browsers, as of September 2018, of HTML elements unique to one of the standards:

<rb><sup><a href="">[74]</a></sup></rb>W3CAll browsers, except Edge
<rtc><sup><a href="">[75]</a></sup></rtc>W3CNone, except Firefox
WHATWGAll browsers"[Since] the HTML outline algorithm is not implemented in any browsers ... the 
 semantics are in practice only theoretical."
[77]WHATWGFull support only in Edge and Firefox desktop.

Partial support in Firefox mobile.

Supported in Opera with user opt-in.

Not supported in other browsers.

Experimental technology
<slot><sup><a href="">[78]</a></sup></slot>WHATWGAll browsers, except Edge and IEExperimental technology

Reset Password