- Accessibility
- Authentication
- CSS
- Self-Sovereign Identity
- Virtual Reality
- Linked Data
- XML
I wrote a comment about the W3C's relationship with WHATWG a few days ago: https://news.ycombinator.com/item?id=37052428
If you do nothing else, please pass your eyes over the list of W3C Recommendations and other publications on standards track: https://www.w3.org/TR/
And yes, even VRML :)
https://www.w3.org/MarkUp/html-spec/ HTML 2 (the wild west)
https://www.w3.org/MarkUp/Wilbur/ HTML 3.2
https://www.w3.org/TR/WD-html40-970708/appendix/changes.html Diffs of HTML 3.2 -> 4
https://www.w3.org/People/Raggett/book4/ch02.html History of HTML until 3.2
https://www.w3.org/TR/html401/ HTML 4
https://www.w3.org/TR/html5-diff/ Diffs of HTML 4 -> 5
https://www.w3.org/TR/2021/NOTE-html53-20210128/ HTML 5.3 (last version on W3C)
https://html.spec.whatwg.org/multipage/ HTML5.3+ (moved to whatwg)
https://www.w3.org/MarkUp/VRML/ Virtual Reality Markup Language
W3C is not only about HTML, JavaScript, and CSS.
https://en.m.wikipedia.org/wiki/World_Wide_Web_Consortium#St...
E.g., I don't see WHATWG contributing anything of relevance regarding web accessibility, whereas W3C takes care of accessibility with WAI-ARIA and WCAG.
To actually become a standard it needs at least two inependent implementations.
But it's interesting that you wrote what you wrote. Because that's exactly what Chrome is doing: it's announcing an intent to implement, and then enables whatever they intend by default. Oh, they do pretend to ask other vendors about their position, but ship anyway. And then use web.dev to pretend it's a standard.