4 ms·

It's not. But that's besides the point. The W3C haven't been in the driver's seat for a very long time now when it comes to web standards.

• paulddraper 7y ago
  Well, not spec, but proposed spec. [1] Driven by Google, but under the auspices of W3C. > The W3C haven't been in the driver's seat for a very long time now when it comes to web standards. That was exactly ghostpepper's point. [1] https://github.com/WICG/ScrollToTextFragment https://github.com/WICG/ScrollToTextFragment
  • 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 ago
      We are in violent agreement.
      • tpmx 7y ago
        With the risk of falling into a loop: https://news.ycombinator.com/item?id=22386665 https://news.ycombinator.com/item?id=22386665
    • SahAssar 7y ago
      WHATWG 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.