https://xslt-processor.tradik.com/blog/ @tradik/xslt-processor blog Fri, 02 Oct 2026 08:17:07 +0000 https://xslt-processor.tradik.com/blog/release-1-3/ https://xslt-processor.tradik.com/blog/release-1-3/ Fri, 02 Oct 2026 12:00:00 +0000 Two releases today. @tradik/xslt3 1.0.0 is a new package: XSLT 3.0 and XPath 3.1 in JavaScript, which also runs XSLT 2.0 stylesheets. And @tradik/xslt-processor 1.3.0, the browser XSLTProcessor replacement, can now hand a 2.0 or 3.0 stylesheet to it when you ask. Nothing changes for anyone who doesn https://xslt-processor.tradik.com/blog/xslt3-in-javascript/ https://xslt-processor.tradik.com/blog/xslt3-in-javascript/ Thu, 01 Oct 2026 11:00:00 +0000 Every browser that ever ran XSLT ran version 1.0, the 1999 recommendation. Chrome and Safari used libxslt, Firefox its own TransforMiiX. XSLT 2.0 arrived in 2007 and 3.0 in 2017, with grouping, regular expressions, real functions, maps, JSON and a much stronger XPath, and the browsers never followed https://xslt-processor.tradik.com/blog/xslt-removal-impact/ https://xslt-processor.tradik.com/blog/xslt-removal-impact/ Thu, 01 Oct 2026 10:00:00 +0000 Chrome's case for removing XSLT rests on two numbers: about 0.02% of page loads use XSLT, and less than 0.001% use the xml-stylesheet processing instruction (the background is here). Put that way it sounds like nothing. It is worth looking at what sits behind it before deciding that it doesn't conce https://xslt-processor.tradik.com/blog/chrome-is-turning-off-xslt/ https://xslt-processor.tradik.com/blog/chrome-is-turning-off-xslt/ Thu, 01 Oct 2026 09:00:00 +0000 On 17 November 2026, Chrome 158 reaches the stable channel, and XSLT stops working in it. A page that calls new XSLTProcessor() gets a ReferenceError. An XML file that starts with <?xml-stylesheet type="text/xsl" href="…"?> shows up as raw XML instead of the HTML its author https://xslt-processor.tradik.com/blog/release-1-2/ https://xslt-processor.tradik.com/blog/release-1-2/ Wed, 30 Sep 2026 18:00:00 +0000 Version 1.2.0 went out on 30 September 2026, and 1.2.1 followed a few hours later. The second one exists because of a bug in our own tests, and we will get to that. First, what 1.2 is about: making the JavaScript XSLTProcessor behave like the one Chrome is about to switch off, on the inputs real sty https://xslt-processor.tradik.com/blog/xslt-1-0-surprising-rules/ https://xslt-processor.tradik.com/blog/xslt-1-0-surprising-rules/ Tue, 29 Sep 2026 12:00:00 +0000 XSLT 1.0 is a short specification, and people who have written stylesheets for years still get caught by parts of it. We know, because writing a processor that matches Chrome meant finding every one of these the hard way: the 1.1 releases of @tradik/xslt-processor fixed dozens of them. Here are the