The Role of WHATWG in Modern Web Standards
You'll learn how a breakaway group revolutionized the way web standards are created and maintained today.
Why WHATWG Was Born
By the early 2000s, the W3C (which you learned about earlier) had shifted focus away from HTML toward XHTML and XML-based technologies. Browser makers—particularly those at Mozilla, Apple, and Opera—felt this ignored the real needs of web developers building modern applications. In 2004, they formed the Web Hypertext Application Technology Working Group (WHATWG) to continue evolving HTML in practical, browser-friendly directions.
Think of it like a group of craftspeople who disagreed with the official guild's rulebook, so they started their own workshop to build tools people actually needed.
Living Standards vs. Fixed Versions
WHATWG introduced a revolutionary concept: living standards. Instead of releasing HTML6, HTML7, etc., they maintain specifications that continuously evolve. The HTML Living Standard is always "the current version"—updated incrementally as browsers implement new features and developers provide feedback.
This contrasts with the W3C's traditional versioned approach (HTML 4.01, HTML5). The living standard model means:
- No waiting years for the "next big version"
- Features stabilize individually when ready
- The specification reflects what browsers actually support now
WHATWG Today
WHATWG now maintains several core web standards, including HTML, DOM, and Fetch. Major browser vendors collaborate directly within WHATWG, ensuring standards stay aligned with real-world implementation. The W3C and WHATWG even reconciled their HTML efforts, with WHATWG's HTML Living Standard becoming the canonical reference.
Key Takeaway: WHATWG emerged when browser makers needed practical, evolving standards—introducing the "living standard" model that keeps HTML and other core web technologies continuously updated rather than frozen in versioned releases.