53
Should we remove XSLT from the web platform? (github.com)
submitted 1 year ago by to c/technology@lemmy.world
9 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.bestiver.se/post/555312

Comments

My comment: It seems google is trying to pull another Manifest v3 and JPEGXL - propose then ignore everyone and do it anyway.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (3 children)

Why not fix library, corporate are lacking of founds to fix all the tickets ? Reminds me of Google openssl fork because it's not "their" opensource product so they won't contribute or pay someone to do it.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago (2 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •