Comment on W3C declares HTML5 standard completeparentComments−greyfade11yEqually authoritative? I had no idea WHATWG was drafting specifications, let alone considered authoritative.−domenicd11yMany of the foundational specifications of the web are authored and maintained by the WHATWG these days: https://spec.whatwg.org/- DOM, HTML: obvious- URL, Encoding, Fetch: foundational building blocks- XHR, Fullscreen, Notifications: important featuresThere are also other up-and-coming specs like Books, Figures, Streams, or Loader (the latter two not listed).−edwintorok11yThe spec site doesn't load for me on Firefox with RC4 disabled: Cannot communicate securely with peer: no common encryption algorithm(s). (Error code: ssl_error_no_cypher_overlap)−coldtea11yWell, perhaps you haven't kept up then. It's a while since W3C was considered either authoritative or relevant for the modern web.HTML5 is most all WHATWG.
Comments
Equally authoritative? I had no idea WHATWG was drafting specifications, let alone considered authoritative.
Many of the foundational specifications of the web are authored and maintained by the WHATWG these days: https://spec.whatwg.org/
- DOM, HTML: obvious
- URL, Encoding, Fetch: foundational building blocks
- XHR, Fullscreen, Notifications: important features
There are also other up-and-coming specs like Books, Figures, Streams, or Loader (the latter two not listed).
The spec site doesn't load for me on Firefox with RC4 disabled:
Well, perhaps you haven't kept up then. It's a while since W3C was considered either authoritative or relevant for the modern web.
HTML5 is most all WHATWG.