Firefox started showing a message "XSLT will be removed from this web browser soon" (mozilla/standards-positions#1287) . Blink (chromium) is likely to follow too (https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4gYZeSJA) and Webkit also expresses initial support for removal of XSLT.
The working group for HTML living standard is discussing the issue here: whatwg/html#11523
An article also appeared on LWN: https://lwn.net/Articles/1034560/
This has serious implications for CLAM which currently fully relies on client-side XSLT to render the web interface. So when browsers drop XSLT support, all CLAM services will break. The remedy would be to move this rendering server-side, although that goes counter to CLAM's original design, but that admittedly, is rather dated.
A less obvious and far more time-consuming option would be to develop a more modern and minimalistic alternative to CLAM entirely, without any XSLT.
Firefox started showing a message "XSLT will be removed from this web browser soon" (mozilla/standards-positions#1287) . Blink (chromium) is likely to follow too (https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4gYZeSJA) and Webkit also expresses initial support for removal of XSLT.
The working group for HTML living standard is discussing the issue here: whatwg/html#11523
An article also appeared on LWN: https://lwn.net/Articles/1034560/
This has serious implications for CLAM which currently fully relies on client-side XSLT to render the web interface. So when browsers drop XSLT support, all CLAM services will break. The remedy would be to move this rendering server-side, although that goes counter to CLAM's original design, but that admittedly, is rather dated.
A less obvious and far more time-consuming option would be to develop a more modern and minimalistic alternative to CLAM entirely, without any XSLT.