TextFormatter uses XSLTProcessor, which might get deprecated/removed from browsers

[mfreed7]

Hello, I'm reaching out to point out that TextFormatter, specifically right here:

• https://github.com/s9e/TextFormatter/blob/master/src/render.js#L7

uses XSLTProcessor. There's a discussion happening about whether to deprecate that API from browsers. So I wanted to point that out, and perhaps suggest including a polyfill or other workaround, so that in case it does get removed from browsers, no TextFormatter functionality is lost.

I found this library via several sites that appear to use it, and appear to be broken if XSLTProcessor is removed:

• https://nothing.community/
• https://tvheadend.org/
• https://telekomunikace.cz/
• https://reflot.es/

There are a few options for JS-based XSLTProcessor implementations

• Saxonica
• A WASM polyfill I wrote
• Likely others

Happy to answer questions if needed.

[JoshyPHP]

Hi,

Thanks for the heads-up. I'm going to kick the can down the road on this one but I'll look into using a polyfill whenever major browsers start dropping support.

[mfreed7]

Thanks for the heads-up. I'm going to kick the can down the road on this one but I'll look into using a polyfill whenever major browsers start dropping support.

Ok, thanks! There is time. But Chrome now plans to turn off support in v155, around Nov 2026. And much earlier than that in pre-stable (e.g. Beta) channels. Anyway, I appreciate the comment, and let me know if I can answer any questions about the polyfill when the time comes.