I am aware of the notice made by Chrome to remove XSLT support in 2026. I believe that I have seen comments to the effect that Firefox will follow suit. Here is the link to the notice [ https://developer.chrome.com/docs/web-platform/deprecating-xslt ].
On the surface, this decision seems counter to the open web, and W3C standards.
From forum posts, I am seeing that there is the beginnings of a plan for continuation of XSLT support in Chrome after deprecation, with a combination of plug-in, pinned version of Chrome, etc.
Given the history of Mozilla in supporting open source and open computing, I would expect that there would be a continuation plan XSLT in Firefox as well. The continuation plan could include: keeping XSLT support, refactoring XSLT support into an optional browser plug-in (as Chrome plans to do), etc.
Why would providing a path for continuation of XSLT support in Firefox be important? The most obvious answer is that there has been no statement of user or economic impact provided with the deprecation announcement. Anecdotally, concerns have been expressed in forum posts about impact to financial, telecom and cybersecurity related uses of XSLT based applications. On a personal note, yesterday I was advised to download an archive of my medical records because of a medical portal migration. Upon opening the zip file, I found that the records were in XML, with an XSL stylesheet for formatting... which will cease to work later this year.
I just read the Mozilla mission... Our mission is to ensure the Internet is a global public resource, open and accessible to all. An Internet that truly puts people first, where individuals can shape their own experience and are empowered, safe and independent. What is is going to be?