Chrome is deprecating client-side support for XSLT, which K2 uses in design time and runtime experiences. Fix packs will be released for all supported K2 versions so that K2 will continue to function after the XSLT deprecation on November 17, 2026.
There are several workarounds to extend this, based on Chrome’s features, which you can utilize if you cannot upgrade to a supported version with the necessary fix pack.
Short Term: Enterprise Policy Controls
- Using standard administrative Chrome Enterprise controls, you can continue XSLT execution by setting the specific enterprise policy dedicated to XSLT preservation inside your Google Admin Console or Group Policy. Search for “XSLT” in chrome://flags/
- Google also offers an official XSLT Polyfill Extension. Administrators can force-install this extension via the Chrome Apps and Extension Management policy to preserve functionality.
- You can also freeze browser versions at the last compatible version via Group Policy.
Long Term: Upgrade to a K2 Supported Version and Fix Pack
We will be releasing fix packs for supported K2 versions to follow the development practices from Google. As these fix packs are released, we will update this article and post links here. All versions from K2 (5.10) on will have this fix included.