4 ms·
But 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 re
by ChrisSD 9y ago
But 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.