August 1st - Googler asks the community if XSLT should be removed from the HTML living standard.
github.com/whatwg/html/issues/…
Respondents overwhelmingly reject the suggestion.
August 6th - Google starts work on removing XSLT from Chrome.
issues.chromium.org/issues/435…
August 14th - Googler sends PR to remove XSLT from the standard.
github.com/whatwg/html/pull/11…
Like, I don't have a particular view of whether this is a good idea or not. But these sham community engagement exercises piss me off.
Should we remove XSLT from the web platform?
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...mfreed7 (GitHub)

Terence Eden
in reply to Terence Eden • • •As a little bonus treat, here's an older discussion about Google removing XSLT from Blink.
Most of the arguments (on both sides) remain the same.
groups.google.com/a/chromium.o…
The date of that discussion? 2014!
Intent to Deprecate and Remove: XSLT
groups.google.comLisPi
in reply to Terence Eden • • •1) move away from Github
2) remove Google from the list of contributors.
LisPi
in reply to LisPi • • •Cassandrich
in reply to LisPi • • •Haelwenn /элвэн/
in reply to Cassandrich • • •True that said I'm not sure WHATWG really has a consensus building process, case in point the last few comments being marked off-topic and then discussion locked while they point that libxslt has a lack of maintenance.
What I see is Google effectively answering "Fuck off" to the "Fuck you pay me" of libxslt maintainer, and WHATWG (mostly Google but not only) supporting that.
Oblomov
in reply to Haelwenn /элвэн/ • • •@lanodan @dalias @hokaze @lispi314
The WHATWG in theory has a consensus building process in the sense that one implementor against would block the progress. But who's going to do it? The only “independent” implementor there is Mozilla and that's controlled opposition.
Haelwenn /элвэн/
in reply to Oblomov • • •As far as I can tell WHATWG is steered by Apple, Google, Microsoft, Mozilla.
github.com/whatwg/sg#steering-…
And given M$ is still there, independent implementation doesn't matters.
GitHub - whatwg/sg: A place to raise issues with the WHATWG Steering Group
GitHubHubert Figuière
in reply to Haelwenn /элвэн/ • • •PointlessOne
in reply to Terence Eden • • •It's a very selective approach to dropping parts of web. Chrome still supports <plaintext> tag that has been deprecated in HTML 2 (1995). And the tag does some wild stuff to HTML parsing. I'm also confident its usage is much lower than XSLT. Somehow no one's calling for removing its support.
developer.mozilla.org/en-US/do…
The security argument is a bit disingenuous, too. First Google unleashes Project Zero on libxml/libxslt. They unload a whole bunch of security issues on the maintainer, propose no fixes. And now declare the project poorly maintained and insecure. Google has resources to fix all the issues and help maintain the libs. They have resources to write a new XML/XSLT lib in a safe language of their choice.
They just don't want to. And if they don't want, no amount of evidence or arguments can change that.
They started with "we want XSLT dropped” and then reasoned backwards to find some plausible arguments. Not started with the arguments that led to the conclusion that removing XSLT is overall the best solution.
: The Plain Text element (Deprecated)
developer.mozilla.org