4 ms·
The problem with the W3C version is that it isn't even a snapshot of any version of the WHATWG document. The W3C has modified it in some arbitrary ways which do
by duskwuff 9y ago
The problem with the W3C version is that it isn't even a snapshot of any version of the WHATWG document. The W3C has modified it in some arbitrary ways which don't correspond to any "ground truth" in browser implementations.
A practical example: The W3C "spec" says that the <main> tag must only appear once in a document. WHATWG and browsers agree that multiple <main> tags are perfectly fine, albeit silly.
- goblin89 9y agoI don’t read the rest of W3C’s spec to be honest. It’s useful to have a brief summary of changes to see where things are heading (and any convenient changelog implies some kind of versioning), but I’d likely be checking MDN or WHATWG for specifics if something catches my eye. For example, after I saw the new <dialog> tag in W3C’s changelog, I jumped to MDN to find a friendly overview of its usage and a compatibility table (spoiler, the tag isn’t supported by most major browsers).
- ChrisSD 9y agoBut in practice that isn't a good example. Given HTML's extreme error tolerance the practical difference is zero. It only makes a difference for authors, who really should consider it an error to use more than one <main> tag.
- Touche 9y agoThat seems like something to note in a "best practices" guide/book, not in a document that describes how HTML is parsed.
- nkkollaw 9y agoUnless all major browsers agree on how <main> is parsed. Then that's how it's parsed.
- chubot 9y agoExactly, there's a difference between a document for browser implementers and a document for end users/document authors. No end users are going to read EITHER spec.
- nitrogen 9y agoNo end users are going to read EITHER spec. As an end user/engineer I occasionally refer to either spec when something isn't clear otherwise. It was by referring to W3C and WHATWG specs that I wrote a text-synced audio player a few years ago, for example.
- mirekrusin 9y agoBut w3c on this link says: „Multiple main elements in the DOM, so long as only one is visible to the user.” - so they allow multiple main elements as long as single one is visible, right?