News for hackers. Stuff that matters.

mattur

For anyone confused about how the WHATWG came to write a new HTML spec entirely from scratch, after the W3C blocked the work happening at the W3C, this is a good place to start: http://diveintohtml5.info/past.html#webapps-cdf

I'm going to assume your point that the WHATWG is "extremely powerful" compared to the W3C was meant to be satirical.

The machinations behind this have being going on for years, and go much deeper.

Two chairs of the W3C's Web Platform Working Group, who both also happen to be members of the W3C Advisory Board which oversees the W3C Process, appear to have decided it's fine for them to routinely ignore the W3C Process.

Both these individuals seem to be using their positions in the W3C to pursue some kind of personal vendetta. Of course, in theory the W3C Process exists to prevent this kind of thing from happening.

One of these individuals also happens to be a W3C ex-staffer. You can read a somewhat unfavourable summary of this ongoing farcical situation (by a current W3C staff member) here: https://freenode.logbot.info/whatwg/20160614#c998179

The W3C's HTML standard is a buggy, outdated copy of the upstream WHATWG standard.

In the copy-and-paste process the W3C regularly introduces errors which prevent the W3C copy from being used as an implementation reference, even as an outdated standard. Example: https://github.com/w3c/webauthn/issues/257

So the W3C copy is not authoritative, nor can it be in its current state, regardless of what the EU or anyone else says.

The WHATWG standards are the authoritative implementation references. The W3C specs are buggy, outdated, incomplete copies and that looks unlikely to change for HTML, DOM or any other specs the W3C takes from WHATWG and republishes with the W3C logo.