News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by colanderman on Friday April 13, 2018 @10:17AM (#16830198)
> The WHATWG has always opposed the W3C's spec. They see it as confusing to have two "official" specifications.

As the old joke goes... if it hurts, they should stop doing that!

The WHATWG spec is worse than useless to me as a developer. It's impossible to tell what is usable and what is just Google's wishlist (which is about half of it). The MDN has entirely replaced it for me, since they at least do a good job of documenting reality.

WHATWG should quit trying to bully the W3C out of the field, and instead clearly mark the WHATWG "spec" as what it is: a public notepad for browser developers. Leave the business of documenting what browsers actually conform to to the W3C.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by dragonwriter on Friday April 13, 2018 @12:57PM (#16831769)
> The WHATWG spec is worse than useless to me as a developer. It's impossible to tell what is usable and what is just Google's wishlist (which is about half of it). The MDN has entirely replaced it for me, since they at least do a good job of documenting reality.

The WHATWG living standard is largely where browser vendors (and other interested parties) work out what the web will be. W3C (with their implementation requirement), and, as you note, MDN serve to describe what the Web is. The latter is more useful to developers, but, as you suggest, MDN is doing a better job of it.

OTOH, to get to a place where things have interoperable implementations, a forum for implementors to collaborate on forward-lookong specifications is necessary, and that’s what WHATWG does well, and W3C does not (which is why WHATWG exists.)

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by colanderman on Friday April 13, 2018 @03:01PM (#16832968)
I agree with everything you said. What rubs me the wrong way about the WHATWG is that they give the perception (and it may be just that) that they are trying not just to serve as that forum for browser makers, but also as the standard reference for web developers (which is the role the W3C HTML specs, save XHTML 2, have historically served), and doing a poor job of the latter.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by dragonwriter on Friday April 13, 2018 @03:28PM (#16833193)
I don't think the WHATWG is trying to serve as the reference for web developers (though their HTML spec has notable and laudable features for that use); I think they are mostly fine with W3C trying to do that as long as they do it correctly (which requires alignment with what browsers do, otherwise developers will target a non-existent platform.)

I don't know if they (or developers, MDN is probably a more widely used reference than W3C) see a standards body as essential in that role, though, and I don't think it seems W3C really wants to accept being relegated to that role rather than driving the web platform, even though they haven't driven the platform for a long time.

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?

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by ghostly_s on Friday April 13, 2018 @01:33PM (#16832100)
> Leave the business of documenting what browsers actually conform to to the W3C.

Documenting the prevailing conditions is very much not the purpose of a standard.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by colanderman on Friday April 13, 2018 @02:21PM (#16832562)
That's what the W3C has historically done, with HTML 2.0, 3.2, and 4.0. "Document, clean up, and nudge" is maybe a better description. The WHATWG today seems to take more of a "document, don't clean up, and add our wishlist" approach. (The "don't clean up" mentality is embodied in their "don't break the web" ethos; the "add our wishlist" mentality is a consequence of the "living standard" ethos… the "standard" never becomes reality because it is constantly changing.)
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by annevk on Saturday April 14, 2018 @12:19PM (#16837974)
I'm not sure where you got this impression, but it's wrong. https://whatwg.org/working-mode stipulates the requirements on additions. That's quite a bit different from a set of wishes.

And there's a lot of cleanup of legacy APIs happening too. E.g., removal of the isindex tag and deprecation of AppCache.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by ttepasse on Friday April 13, 2018 @01:46PM (#16832228)
That is the governing philosophy of the WHATWG, sadly.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by annevk on Saturday April 14, 2018 @12:21PM (#16837984)
That's a bit of a stretch. This is only relevant to legacy APIs and only when all implementations are in agreement, which is quite the rarity.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by coding123 on Friday April 13, 2018 @11:23AM (#16830822)
I think that's the rub - if w3c wants to "document" what a browser conforms to - I imagine it will be a copy-paste from what the browser vendors are doing in their separate meetings of the minds.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by y4mi on Friday April 13, 2018 @10:58AM (#16830558)
Urm, I thought MDN was based on WHATWG? (Not W3C)
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by colanderman on Friday April 13, 2018 @11:28AM (#16830893)
MDN includes clear documentation about what is actually implemented in all major browsers (the compatibility tables), so I (as someone who wants my code to work everywhere now, not next year) can tell at a glance what pie-in-the-sky ideas I should ignore.

That's great that it's based on the WHATWG's work – it should be, since it should document what's in Firefox, and Firefox presumably is following their own work with the WHATWG. But the WHATWG shouldn't pretend that they're useful to me in any other way than a preview of what's coming down the pipeline. For that, I need clear documentation of what is, not what will be. W3C HTML specs prior to HTML 5 (with the exception of the abortion that was XHTML 2) have historically served that purpose well. It was easy to make the judgement that, once my target market primarily supported HTML 4, I could use anything in that spec. The WHATWG "spec" throws that idea out the window.

Ideally, with a "living standard", periodically there are snapshots of some form that document what all or most major browsers supported as of some point in time. So I as a developer can say, "well I know most of my target market have updated their browsers since date X, so I can just use anything in this standard snapshot". The W3C I think is trying to do this. They might not be doing a very good job (indeed that is the crux of the WHATWG's objections); like I said, I personally rely on MDN to fill this same role for me. But the WHATWG living standard itself cannot fill this role, short of including MDN-style compatibility tables, or making their own snapshots that are somehow "better" than what the W3C puts out.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by annevk on Friday April 13, 2018 @12:44PM (#16831647)
FWIW, the HTML Standard (not the DOM Standard) does include CanIUse information in a sidebar, to help with this. I'd like to include this into other WHATWG standards, but it hasn't really happened yet. I'd expect most web developers to use MDN and StackOverflow though, as you say.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by colanderman on Friday April 13, 2018 @01:35PM (#16832118)
I appreciate the attempt to include compatibility tables, but they're nowhere near detailed enough for serious usage. Take the canvas element as an example. The WHATWG spec has one "CanIUse" sidebar for basically each section, if that. But compatibility issues exist at the level of individual methods. E.g. .filter and .resetTransform() both have very low cross-platform support ([1] and [2]), which I can tell at a glance from MDN, both in the sidebar listing them, and the compatibility tables on each page. Whereas the WHATWG spec doesn't even mention that these are experimental ([3] and [4]), and the CanIUse sidebar is totally absent for them.

StackOverflow is not a reference, and the answers for even popular queries are sometimes a decade out of date.

[1] https://developer.mozilla.org/en-US/docs/Web/API/CanvasRende...

[2] https://developer.mozilla.org/en-US/docs/Web/API/CanvasRende...

[3] https://html.spec.whatwg.org/dev/canvas.html#dom-context-2d-...

[4] https://html.spec.whatwg.org/dev/canvas.html#transformations