Xslt

Chrome 158 drops native XSLT — XSLTProcessor and xml-stylesheet stop working. Who is actually affected, honest pros and cons of the WASM polyfill vs server-side migration paths, and how to test your stylesheets outside the browser today.

FreeFormatter.com shut down in 2026. Here is what happened, a feature-by-feature mapping of its XSL Transformer to XSLT Playground, and a runnable example — including real Saxon XSLT 2.0/3.0, which FreeFormatter never had.

SWIFT retired MT940/942/101 in November 2025, and ISO 20022 is XML — which is why payments teams are writing XSLT in 2026. A runnable camt.053-to-CSV example in XSLT 2.0, plus trace-based debugging tips.

Peppol and EN 16931 validation is Schematron compiled to XSLT 2.0 stylesheets that emit SVRL. How the multi-layer pipeline works, how to run a compiled rule against a UBL invoice in the browser, and where an online playground honestly fits.

The XML parser found characters before the XML declaration or root element: usually a UTF-8 BOM, stray whitespace/text, or a file that is not XML at all (an HTML error page, for instance).

doc() or document() could not load the requested document: wrong relative URI, missing file, or an environment (like an online tool) with no filesystem access.

A cast or constructor function received a value it cannot convert — casting text to a number or date is the usual suspect. Guard with 'castable as' or use number().

The pattern given to matches(), replace(), tokenize() or xsl:analyze-string is not a valid XPath regular expression — watch out for curly braces in attributes and unsupported constructs.

There is content after the closing tag of the root element — usually two XML documents concatenated, or a fragment list without a wrapper element.

A Saxon wrapper code: the source document failed to parse as XML. The real diagnosis is in the underlying parser message that follows the code.