News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by tptacek on Friday April 13, 2018 @03:29PM (#16833206)
Exactly what is the purpose of a standard reference for web developers that fails to track the documented behavior of browsers?
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by colanderman on Friday April 13, 2018 @07:31PM (#16834829)
I'm not sure the intent of your comment; failure to track what browsers actually do is exactly the problem with the WHATWG "living standard" – it's very much a forward-looking spec at best, and too often a wishlist.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by ubernostrum on Saturday April 14, 2018 @05:16PM (#16839564)
The ideal situation is for the WHATWG document to be a roadmap of what vendors have discussed and tentatively agreed on, and the W3C document to be a periodic snapshot of what's actually been implemented.

That wouldn't make either one of them "bad". The issue here seems to be W3C wanting to push forward things that the vendors haven't agreed on or implemented yet.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by mcchampion on Sunday April 15, 2018 @12:59PM (#16843527)
I don't think the W3C DOM document has anything the developers haven't agreed to. The problem is that it's an incomplete, intrinsically out of date, and often buggy subset of the the WHATWG living standard.

I agree that the W3C value proposition COULD be to publish a snapshot that describes what's actually implemnted. That might be a way forward here, but it requires a lot of work to define what "actually implemented" means in a useful way, and to check the test results and update the document (or build an automated way to harvest resources such as https://wpt.fyi/dom ).

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Saturday April 14, 2018 @08:09AM (#16836982)
Great, so if I build a website based purely on the WHATWG specs, it will work in all browsers, correctly?

No, it won't.

I can take the A4 paper spec and build a printer that takes that paper, and I know paper will comply with it. And the other way around.

You can't build a website just from WHATWG specs, and you can't, excluding the parts about backwards compatible parsing, easily build a new browser from scratch either.

A standard is an a-priori written document that describes the entire API surface, so that people on both sides can develop based on the standard without having to verify with actual implementations.

The WHATWG documents are useless for this purpose.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by chrisseaton on Saturday April 14, 2018 @02:26PM (#16838691)
But how are the W3C specs any better than the WHATWG specs?

As far as I know the W3C take the WHATWG specs, and modify them with some of their own ideas so they're different from the what the browsers implement or are planning to implement.

What on earth is the point of that? Why design your own spec that nobody is implementing or planning to implement? What a waste of time!

And back to your point - why is it better than the WHATWG specs?