In case you're wondering, the HTML WG charter hasn't been extended beyond December, 6th. There hadn't been any public activity for about two years anyway and W3C had undergone major changes meanwhile, such as a change in financing and legal entity type.
Worth noting is that privacy concerns related to the reporting and other APIs were what was preventing the last considered WHATWG HTML Review Draft (published January, 2022) to become a recommendation, and change in HTML's so-called outlining (a holdout of Ian Hickson's vision for HTML that was never implemented in browsers and accessibility tech). Even though Steve Faulkner took it upon himself to remove outlining in upstream WHATWG specs, now no W3C recommendation is representing a modern HTML language without outlining. [1] makes the point that, arguably, its removal would've warranted a major version bump ("HTML 6") anyway, considering outlining has been formally part of "HTML 5" for the longest time.
Once web development moved to the WHATWG, it's not obvious what continued relevance W3C had. Nobody was particularly waiting on their blessing or rubber stamp.
The W3C was not, for instance, a useful bastion against things like DRM, because they approved the EME DRM mechanism. And they weren't doing new web innovation that people wanted. So what purpose did they serve?
That the W3C wasn't a useful bastion against DRM is an understatement. It was the main driving force. WHATWG, on the other hand, appears to have opposed it.
A few tech companies have outrageous _corporate_ influence in the W3C who shouldn't.
To name a few: Google, Microsoft, Netflix.
I predicted serious issues with this ages ago, to the point that I suggested the best thing for humankind would be a fork of the HTML spec on behest of WHATWG. I also remember some long time independent contributors like Anne van Kesteren agreeing to this at the time.
This is a capstone of sorts to a process begun by the W3C's XHTML focus 20 years ago. Once again, incremental improvements to a flawed technology (HTML) were more successful than a perfectionist rewrite (XHTML). We so often ignore or downplay costs associated with adoption and migration when we build our "castles in the air".
> The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures. (Fred Brooks)
The W3C HTML working group was even further removed from users, imagining castles but then delegating the building to others.
You're not wrong. The W3C was focused on DTDs and semantic markup and whether HTML "validated" or not. They were focused on moving folks from "transitional" XHTML to "strict" XHTML with no perceivable benefit. Meanwhile the WHATWG was interested in things like media tags and making interactive content be things other than Flash and Silverlight and Java.
They got too lost in the sauce with what was essentially an academic exercise that didn't really benefit the end user.
No, imposing structure onto markup using DTDs had always been a useful and elegant technique.
What W3C was busy with after subsetting XML from SGML as a canonical subset not requiring markup declarations/DTDs for mere parsing (which while useful was already possible and practiced using SGML profiles) is inventing ill-conceived modularization and meta conventions (namespaces, xsi, xinclude), entirely new schema and transformation/query languages, unrealistic and unproven design-by-comittee formatting and browser interactivity systems, and enormous enterprise messaging system ecosystems.
Maybe, but who does it benefit? What is the outcome for people using the web? How were the developers making websites benefiting? It wasn't a bad effort but it was focusing on something that didn't actually solve the biggest problems with the web. XHTML wasn't built for anyone real, it was built for an idealistic outcome.
Private companies (Adobe, Sun, Microsoft, Real, Apple) had a literal monopoly on video and animation on the Web. A lack of interface between JavaScript and the DOM led to companies like Microsoft freely inventing their own stuff.
If you want to be the steward of a technology, you have to care about the way people are actually using the technology. Otherwise someone else who actually does care will (and did!) come along and do something meaningful.
Users being anyone using the web. HTML 5's initial draft, which was the beginning of the end for the W3C, was published in January 2008. Chrome was released in September 2008.
HTML 5 became a W3C recommendation in 2014, when Chrome had less than a 40% market share.
The whole point is that the W3C has been impotent when it comes to HTML for a decade now. They're not publishing anything Google wants in that domain because they're not publishing anything. HTML was taken out of the W3C's control because of their mismanagement it well before Google had a browser majority (let alone a monopoly).
Because browser vendors refused to implement XHTML properly, and then Mozzilla folks pushed for HTML5 outside W3C, Web freedom, what an irony than now Google plays Simon says.
That's false. Browser vendors implemented XHTML so the Web wasn't a broken mess. You can't force developers to write perfect markup. XHTML had lots of undefined behavior and bad failure modes. Implementing XHTML "properly" meant breaking the web, but that's not what the W3C cared about, they cared about standards for standards sake.
Let me be clear: XHTML didn't materially benefit anyone at all except the people who were putting their names on a standard. HTML 5 actually fixed real problems. It made parsing HTML sensible and exhaustively defined. It added open features that companies like Macromedia, Apple, Real, Sun, and Microsoft had a monopoly on for a decade prior. Unlike the W3C, the WHATWG made actual, real life people's lives meaningfully better.
Moreover, most of the things Google is pushing for aren't HTML. Protected Audiences—the ad targeting API Google wants—is sitting in front of the W3C folks as part of the WICG.
Developers will do whatever browser vendors push them to do, and they clearly decided they did want to push HTML5 agenda instead.
Now, Firefox is for all purposes dead, just fairing a bit better than The Year of Linux Desktop, Safari with Apple doing its own thing thanks iDevices market share, and everyone else is basically a reskinned Chrome, or Electron garbage, solidifying ChromeOS as the future we all deserve to have, as the IE lesson is long forgotten.
I remember they re-launched as a public-interest non-profit organization. [1] And then that was it. It doesn't seems the WHATWG were interested to play along.
Practically speaking the internet is now Webkit or Blink. With a pitch of Gecko added.
Nearly 25 years after IE 5.5, I do sometimes feel the Web hasn't actually moved or improved as much as we thought it would.
Worth noting is that privacy concerns related to the reporting and other APIs were what was preventing the last considered WHATWG HTML Review Draft (published January, 2022) to become a recommendation, and change in HTML's so-called outlining (a holdout of Ian Hickson's vision for HTML that was never implemented in browsers and accessibility tech). Even though Steve Faulkner took it upon himself to remove outlining in upstream WHATWG specs, now no W3C recommendation is representing a modern HTML language without outlining. [1] makes the point that, arguably, its removal would've warranted a major version bump ("HTML 6") anyway, considering outlining has been formally part of "HTML 5" for the longest time.
[1]: https://sgmljs.net/blog/blog2303.html