WHATWG: The Browser Vendors' Standards Effort

In the early 2000s, the W3C's official successor to HTML was XHTML 2.0 — a deliberate clean-slate redesign that dropped backward compatibility with existing HTML content and browser behavior in favor of stricter, more theoretically 'correct' markup rules.

Apple, Mozilla, and Opera, the browser vendors who had to actually support the real, messy, existing web, judged this direction impractical: billions of existing pages would simply break. In 2004, they formed the Web Hypertext Application Technology Working Group (WHATWG) to pursue an alternative: evolving HTML compatibly, building new capabilities on top of what already worked rather than replacing it wholesale.

For roughly 15 years, the W3C and WHATWG maintained parallel, occasionally diverging HTML specifications — a genuinely confusing situation for browser implementers and spec readers alike, since the two documents could disagree on specific details.

In May 2019, the W3C and WHATWG formally agreed that the WHATWG's continuously-updated 'HTML Living Standard' would become the single, authoritative source going forward, with the W3C ceasing independent publication of a separate HTML specification. This resolved years of ambiguity and established a clear single source of truth.

WHATWG's steering group is composed directly of the organizations that build major browsers — Apple (Safari), Google (Chrome), Mozilla (Firefox), and Microsoft (Edge) — a notably tighter governance structure than the W3C's broader, more diverse membership model.

This structure keeps specification work closely tied to real-world implementation constraints: a feature proposed for the HTML Living Standard is being evaluated directly by the engineers who would need to actually build it into a shipping browser, rather than by a more theoretical or purely academic standards process.

Born From Browser Vendor Frustration. WHATWG formed in 2004 when Apple, Mozilla, and Opera grew frustrated with the W3C's direction — which had shifted toward XHTML 2.0, a clean-slate, backward-incompatible redesign — and started an alternative, browser-vendor-driven effort focused on evolving HTML pragmatically instead.

WHATWG Formed In Direct Response To XHTML 2.0. In the early 2000s, the W3C's official HTML successor effort, XHTML 2.0, deliberately broke backward compatibility with existing web content. Browser vendors, who had to support the real web as it existed, judged this impractical and started WHATWG to pursue a compatible evolutionary path instead.

Why WHATWG Formed. What was the core disagreement that led browser vendors to form WHATWG separately from the W3C in 2004?

• →A dispute over W3C membership fees
• →Disagreement over backward compatibility: XHTML 2.0 broke it, browser vendors needed it preserved
• →There was no real disagreement; it was purely organizational

WHATWG Eventually Became The Sole Steward Of The HTML Spec. For years, the W3C and WHATWG maintained separate, occasionally diverging HTML specifications — a genuinely confusing situation for implementers. In 2019, the W3C and WHATWG signed a formal agreement making the WHATWG's 'HTML Living Standard' the single, authoritative source.

Resolving Dual Specifications. What happened in 2019 that resolved years of the W3C and WHATWG maintaining separate HTML specifications?

• →The W3C was formally dissolved
• →A formal agreement made WHATWG's Living Standard the sole authoritative HTML spec
• →The situation remains unresolved with two competing specs today

WHATWG Is Governed By Major Browser Vendors Directly. Unlike the W3C's broader membership model, WHATWG's steering group is composed directly of the organizations that actually ship browsers: Apple, Google, Mozilla, and Microsoft — putting specification decisions in the hands of the entities responsible for real-world implementation.

WHATWG Governance. Why might having browser vendors directly govern the HTML specification (rather than a broader, more general membership) be considered an advantage?

• →There's no meaningful advantage to this structure
• →Decisions stay closely aligned with real-world implementation feasibility and constraints
• →It simply allows specs to be written faster with less prose

WHATWG Understood. You now understand WHATWG's origin as a pragmatic, compatibility-focused alternative to XHTML 2.0, its 2019 emergence as the sole authoritative steward of HTML, and its distinctive browser-vendor-direct governance model.

Follow The WHATWG Baseline Requirements. Every conforming page declares its character encoding and a responsive viewport.