← Back to context Comment by WJW 7 hours ago Yes, because XSLT won't work in Chrome and Edge anymore. 3 comments WJW Reply Klonoar 6 hours ago Their comment isn’t clear if they’re doing the transform on the server before piping it down as HTML, which some implementations have done over the years as it provided access to newer XSLT features that browsers stagnated on. miohtama 6 hours ago You can still run JS or WebAssembly based XSLT transformer genxy 5 hours ago This is what the browser vendors should have done, with links to the wasm modules for doing the transforming. It would have been better this way.
Klonoar 6 hours ago Their comment isn’t clear if they’re doing the transform on the server before piping it down as HTML, which some implementations have done over the years as it provided access to newer XSLT features that browsers stagnated on.
miohtama 6 hours ago You can still run JS or WebAssembly based XSLT transformer genxy 5 hours ago This is what the browser vendors should have done, with links to the wasm modules for doing the transforming. It would have been better this way.
genxy 5 hours ago This is what the browser vendors should have done, with links to the wasm modules for doing the transforming. It would have been better this way.
Their comment isn’t clear if they’re doing the transform on the server before piping it down as HTML, which some implementations have done over the years as it provided access to newer XSLT features that browsers stagnated on.
You can still run JS or WebAssembly based XSLT transformer
This is what the browser vendors should have done, with links to the wasm modules for doing the transforming. It would have been better this way.