Should we remove XSLT from the web platform? · Issue #11523 · whatwg/html
github.com
What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...
  • sugar_in_your_tea@sh.itjust.worksEnglish
    1·
    2 days ago

    Looking through the comments, someone already wrote a polyfill that people could use if they need it. It’s a niche feature that is the source of security vulnerabilities, so why fix it if they can safely replace it?

    • vane@lemmy.worldEnglish
      2·
      1 day ago

      To have good XSLT library that follows standard ? But no we got html5 and now web components and shadow DOM slop that is not even accessible from javascript instead of proper XSLT because nobody wants to deal with it. XPath is broken since the beginning of this shit show.

      • sugar_in_your_tea@sh.itjust.worksEnglish
        1·
        22 hours ago

        It sounds like you’re complaining about not having consistent DOM state, not about the XSLT library. Whether the library is built in to the browser or an add-on is irrelevant to your problem.