Chrome 158 Removes XSLT, Breaking Legacy XML Transforms
Stable on November 17, 2026, Chrome 158 disables XSLTProcessor and the XSLT processing instruction for everyone outside Origin Trial and Enterprise Policy. If a page quietly relied on the browser to turn XML into HTML, it just stopped.
Chrome 158 reached stable on November 17, 2026, and with it, client-side XSLT support stops working for ordinary users. Two browser-facing pieces disappear at once: the XSLTProcessor JavaScript API, and the old <?xml-stylesheet type="text/xsl"?> processing instruction that let an XML document reference a transform and render as styled HTML without a single line of server code. The most common place this shows up in the wild is a WordPress or CMS sitemap: open an XML sitemap in a browser and the readable table you're used to seeing was never a sitemap feature, it was a small XSLT stylesheet the browser applied on the fly.
Whoever owns that sitemap, or any other page leaning on the same trick, finds out about the change the hard way: a page that used to render cleanly now dumps raw XML tags into the viewport. That's a legacy dependency nobody budgeted time for, and it's exactly the kind of platform debt that legacy modernization services exist to surface before a browser update does it for you instead.
What actually changes in Chrome 158
Chrome had been warning about this for over a year before the removal landed. Chromium's own write-up on removing XSLT lays out a staged rollout: Chrome 154, in September 2026, began disabling XSLT by default in WebView Canary, Dev, and Beta channels as an early warning to app developers embedding Chrome's engine. Chrome 158 extends that default to regular Stable releases for everyone except sites running an Origin Trial or enterprises using a policy override. Those two exceptions get a longer runway, through Chrome 176 in August 2027, before XSLT is gone for good.
The motivation is security, not platform tidiness. XSLT in Chromium is implemented through libxslt, an aging C library with a long history of memory-safety vulnerabilities, and it is now one of the few remaining pieces of markup processing that still parses untrusted XML input directly. Removing it closes an attack surface that modern web pages barely use anymore. Firefox and WebKit have each said they intend to follow Chromium's lead and drop XSLT from their own engines too, but as of this release neither has published a removal date, so the same page can look broken in Chrome and fine in Firefox for a while.
What this means for developers
check whether any page you maintain emits raw XML with an <?xml-stylesheet type="text/xsl"?> instruction, including sitemap.xml output from a CMS plugin, RSS/Atom feeds styled for direct viewing, or SOAP-era integrations; those are the pages that will silently start showing raw tags;
search your codebase for XSLTProcessor; any script calling it to transform XML client-side stops working on Chrome Stable starting with this release;
the fix is almost always to move the transform server-side, render the equivalent HTML directly, or drop the styled view in favor of a plain-text or JSON alternative; none of these require XSLT at the browser layer at all;
an Origin Trial or Enterprise Policy buys time but is not a long-term plan, since every major engine has now signaled the same direction; treat the 2026-2027 window as the deadline to migrate, not a reason to wait.
When does this ship / timeline
Chrome 158 reached Stable on November 17, 2026, per Chrome's own deprecation documentation. The warning phase started with Chrome 154 on September 22, 2026, in WebView pre-stable channels; the final cutoff for Origin Trial and Enterprise Policy participants is Chrome 176, scheduled for August 17, 2027. Firefox and WebKit have confirmed intent to remove XSLT as well but have not announced their own milestones, so cross-browser testing is the only reliable way to know whether a given page still renders correctly today.