If I understand correctly, Mozilla and Apple don’t really want to support it either. And the reason for that is, the spec is still at XSLT 1.0, which is super old, and current implementations are effectively abandonware. Catch-22?

▲

johncolanduoni 2 days ago | parent | next [-]

I believe the spec is at XSLT 3.0 but no browser actually implemented past XSLT 1.0 (not 100% sure - almost nobody cared about this feature last month so hard to find good docs on support). HTML5 and C++ are cut from the same cloth - massive and no reference implementation so full of features that have been “standard” for 10 years but never implemented by anyone.

	▲	notpushkin 2 days ago \| parent \| next [-]
		Yeah, sorry, the XSLT spec is at 3.0 right now of course, but the browsers don’t implement it, and the WHATWG HTML Living Standard only mentions XSLT 1.0.
	▲	arccy 2 days ago \| parent \| prev [-]
		even outside of browsers barely anything supports XSLT newer than 1.0

▲

ekianjo 2 days ago | parent | prev [-]

The spec is at XLST 3 right now.

▲

abraham 2 days ago | parent | next [-]

Browsers only implement XSLT 1

https://meyerweb.com/eric/thoughts/2025/08/22/no-google-did-...

	▲	ekianjo a day ago \| parent [-]
		We were talking about the spec, not the implementation.

▲

JW_00000 a day ago | parent | prev [-]

When notpushkin said "the spec is still at XSLT 1.0", I think "the spec" is referring to the WHATWG HTML Living Standard spec, which only refers to XSLT 1.0. (It wouldn't make sense to say "the XSLT spec is at XSLT 1.0".)