Chrome Beta no longer supports native XSLT processing, so existing XML+XSLT workflows are already broken there. XSLT removal will break multiple government and regulatory sites that rely on proven standards.
I built a drop-in replacement that emulates browser XSLT processing in JS, so existing documents can keep working without rewriting everything into client-side frameworks.
It aims to behave like the built-in XSLTProcessor API and XML stylesheet PI handling, but without relying on the deprecated browser implementation.
This exists mostly because 'just remove it for security' turned out to be less useful than 'make it keep working'.
Chrome is deprecating native XSLTProcessor (warnings in 143+, full removal in 164/Aug 2027). { https://developer.chrome.com/docs/web-platform/deprecating-x... }
Chrome Beta no longer supports native XSLT processing, so existing XML+XSLT workflows are already broken there. XSLT removal will break multiple government and regulatory sites that rely on proven standards.
I built a drop-in replacement that emulates browser XSLT processing in JS, so existing documents can keep working without rewriting everything into client-side frameworks.
It aims to behave like the built-in XSLTProcessor API and XML stylesheet PI handling, but without relying on the deprecated browser implementation.
This exists mostly because 'just remove it for security' turned out to be less useful than 'make it keep working'.
Feedback and breakage reports welcome.