cross-posted from: https://lemmy.bestiver.se/post/555312
My comment: It seems google is trying to pull another Manifest v3 and JPEGXL - propose then ignore everyone and do it anyway.
(tldr: libxslt is a significant source of vulnerabilities and it should absolutely be removed from browsers ASAP.)
What do you guys need this for? And why?
For reformatting / transforming data. If your original data is already in XML then XSLT can be quite powerful there.
You have my attention, please elaborate.
Some context and discussion here: https://mastodon.social/@Edent/115048990801167629
No, we shouldn’t remove it ffs.
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.
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?
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.
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.
