3 ms·
The W3C doesn't even try to drive features after one browser has implemented them and other browsers are considering them - that's the job of WHATWG.
by telotortium 7y ago
The W3C doesn't even try to drive features after one browser has implemented them and other browsers are considering them - that's the job of WHATWG.
- paulddraper 7y agoWe are in violent agreement.
- tpmx 7y agoWith the risk of falling into a loop: https://news.ycombinator.com/item?id=22386665 https://news.ycombinator.com/item?id=22386665
- SahAssar 7y agoWHATWG is mostly HTML and DOM/browser api:s, ECMAscript is by TC39, CSS is still in W3C, URI schemes (which this is about) are in W3C, as seen in this draft being hosted by WICG, which as far as I can tell is a W3C group. At least that has been my understanding of the situation.