Hello ENOVIA community,

Chrome is removing XSLT/XSLTProcessor support, which may affect legacy ENOVIA pages using XSLT for Grid and Tree rendering.

I created an open-source pure JavaScript replacement:
https://github.com/PulseKCode/xslt-bridge

It supports XSLT 1.0 / XPath 1.0 and is designed to work with existing XSLTProcessor code without modifying every call site.

ENOVIA integration:

1. Add:
   WebContent\\common\\scripts\\xslt-bridge.min.js
2. Add this line at the top of:
   WebContent\\common\\emxNavigatorBaseInclude.inc

This allows existing new XSLTProcessor() calls to use the replacement.

Feedback on ENOVIA-specific compatibility is welcome.