After a long tug of war, W3C says it will not publish future HTML and DOM standards, instead letting the WHATWG, a group of browser vendors, do so
W3C hands over development of HTML and DOM standards to browser vendors (WHATWG). — An industry group made up the four major browser vendors …
Context & Ripple Effects
W3C's retreat on HTML and DOM is the endgame of an authority drain that started years earlier: its 2017 approval of browser DRM triggered EFF's resignation and widespread claims that the consortium had been captured by corporate members, accusations its CEO publicly rejected. That same year, Mozilla, Microsoft, Google, Samsung, and W3C already agreed to unify web documentation under Mozilla's MDN portal — an early sign that the browser vendors were becoming the de facto center of platform work.
By formally delegating future HTML and DOM publication to the WHATWG, W3C concedes that the vendor-run living standard won the long tug of war. The move foreshadowed W3C's own conversion into a public-interest non-profit in 2023, which it framed as imperative to preserve its core mission once its flagship deliverables were gone.
First-order effects
- The WHATWG living standard becomes the single source of truth for HTML and DOM, ending the split-brain era where developers navigated two competing specifications for the same platform.
- W3C loses stewardship of its most foundational deliverable, shrinking its direct relevance to the web platform's core layer to zero.
Second-order effects
- The four major browser vendors now both implement and publish the core specifications, removing any independent check between what Chrome, Firefox, Safari, and Edge ship and what the standard says.
- W3C's remaining value concentrates in adjacent domains like CSS and accessibility, forcing it to redefine itself — which it ultimately did by reorganizing as a public-interest non-profit.
Third-order effects
- Standards governance on the web shifts structurally from multi-stakeholder consortia to implementer-controlled bodies, leaving non-vendor constituencies such as accessibility, security research, and archiving without a seat where the core spec is written — precisely the concerns EFF raised when it walked out over DRM.
- If the pattern holds, other standards organizations face pressure to either hand contested technologies to the groups that build them or risk irrelevance, concentrating de facto rule-making power in a handful of platform companies.
The trend: Web platform governance is consolidating around the browser vendors themselves, with formal standards bodies retreating into niches or restructuring as their foundational mandates migrate to implementer-run groups like the WHATWG.