3 ms·
> WHATWG’s officially recommended[1] ways of keeping up are commit history (quite messy), Twitter feed (primarily channeling commit history as it seems), and—I
by espadrine 9y ago
> WHATWG’s officially recommended[1] ways of keeping up are commit history (quite messy), Twitter feed (primarily channeling commit history as it seems), and—I kid you not—manual diffing of Git revisions.
That is mostly meaningful for browser makers and Web authors that want to interact with the development of the HTML specification.
Web developers that simply want to make things are rather encouraged to search MDN and caniuse.com[0], which provide information about the availability and potential quirks of HTML features across browsers, and link to sections of the appropriate specifications.
[0]: https://github.com/whatwg/html/blob/f8f9c6c222ce79c2f8df185521aaa291c7301419/FAQ.md#how-do-i-know-if-a-particular-feature-in-the-standard-is-ready-to-use https://github.com/whatwg/html/blob/f8f9c6c222ce79c2f8df1855...
- TylerH 9y agoThose are both 3rd party offerings and could disappear at the drop of a hat. It's not a good practice for a standards body to rely on outside parties to write documentation for their work.
- tannhaeuser 9y agoI've created a SGML DTD grammar for W3C HTML 5.1 validation at [1], and am in the process of adding 5.2. This is of course only for checking and normalizing HTML the markup language, rather than a reference for Web APIs and browser behaviors. [1]: http://sgmljs.net/docs/w3c-html51-dtd.html http://sgmljs.net/docs/w3c-html51-dtd.html