← Back to context

Comment by tptacek

10 hours ago

Your argument here includes that browsers should retain native XSLT implementations because non-browsers have bad XSLT implementations?

7 comments

tptacek

Reply
dragonwriter  10 hours ago

I don’t see anything that looks remotely like a normative argument about what browsers should or should not do anywhere in my post that you are responding to, did you perhaps mean to respond to some other post?

My point was that the decision to remove XSLT support from browsers rather than replacing the insecure, unmaintained implementation with a secure, maintained implementation is an indicator opposed to the claim "XSLT isn’t going anywhere”. I am not arguing anything at all about what browser vendors should do.

  • tptacek  9 hours ago

    Is the idea that if they did so, the insecure non-browser XSLT-users could adopt their implementation?

    • dragonwriter  9 hours ago

      The idea is that if they did so, the people using software running in the browser could continue to use XSLT with just the browser platform because the functionality would still be there with a different backend implementation, but instead that in-browser XSLT functionality is going somewhere, specifically, away.

      2 replies →