The Digital Press

Chrome plans to disable XSLT support by default in its next version, requiring users to enable it via a flag, with Google also proposing its removal from the HTML standard.

Why it matters: XSLT’s deprecation in Chrome limits browser-based XML transformations, impacting websites relying on client-side XSL processing.

The big picture: This move reflects a broader trend towards reducing legacy web features to streamline browser engines and security.

The other side: Some developers appreciate XSLT’s utility for theming without JavaScript, but face challenges as support wanes.

Commenters say: Many express concern over losing native XSLT support, sharing projects using it and debating alternatives for XML rendering.