XML Folio / Notebook

The browser changes. Your XML can stay.

Start with the execution path, before choosing a replacement.

XML Folio editorial notes · Reviewed October 15, 2026

Two browser paths to look for

A document may ask the browser to apply an XSL stylesheet through an xml-stylesheet processing instruction. An application can also construct XSLTProcessor in JavaScript. Both rely on the browser’s native transformation engine. A feed reader consuming the same XML is a different path.

<?xml-stylesheet type="text/xsl" href="feed-view.xsl"?>

The current Chrome plan

Checked on 15 October 2026, Chrome’s published plan is to stop native XSLT on ordinary Stable releases in Chrome 158, scheduled for 17 November 2026. Origin Trial and Enterprise Policy participants have a temporary exception, currently ending with Chrome 176 on 17 August 2027. Preview channels and managed environments can differ. Recheck the official Chrome migration page before treating either date as a deployment deadline.

What does not follow from that plan

XML itself is not being removed. Styling XML with a CSS processing instruction is a separate feature. A server or build step that produces HTML before a visitor requests the page does not use the visitor’s native XSLT engine for that transformation. A repository containing an .xsl file is therefore not sufficient evidence of a broken browser path.

For your own site, write down the requested URL, the response content type, and where the transformation executes. Save one normal response and one screenshot with XSLT disabled. The presence of an HTML result alone does not tell you whether the server or browser created it.

Choose the smallest faithful replacement

If the stylesheet produces a simple list of feed entries or sitemap URLs, a separate selected-field reading page may be enough. XML Folio generates that artifact and an omission manifest. It does not execute the stylesheet. You must inspect whether omitted extensions, media, sorting or computed values matter to the old view.

If the stylesheet supplies forms, device controls, calculations or a complex document presentation, keep a transformation engine in the architecture. Investigate a server/build renderer or a suitable browser library or polyfill. Compare the resulting behavior against the original application rather than assuming that a readable table preserves it.

Evidence we actually collected

In an isolated Chrome 156 test, our authored styled sitemap produced its two expected content links when XSLT was enabled. With --disable-features=XSLT, those transformed content links disappeared and the constructor was unavailable. The separate exported HTML remained readable with JavaScript disabled. This is evidence for our small fixture, not a compatibility result for every browser or stylesheet.

Follow the test notes to reproduce the important distinctions, then use the publication guide to retain the original machine endpoint.