Comment by webstrand
3 months ago
It would be incredible if we could pull it into the javascript/wasm sandbox and get xslt 3.0 support. The best of both worlds, at the cost of a performance hit on those pages, but not a terrible cost.
3 months ago
It would be incredible if we could pull it into the javascript/wasm sandbox and get xslt 3.0 support. The best of both worlds, at the cost of a performance hit on those pages, but not a terrible cost.
There's even a JS implementation of XSLT 3.0 already (SaxonJS).
That's pretty cool, its too bad the license is a bit confusing about whether bundling with Chrome or Firefox would be permissible under the license.
This is clearly the Right Thing. So what do you suppose the chance of it happening is?
Not really, because that would add a dependency on Javascript whereas, at the moment, XSLT works without Javascript enabled.
Not necessarily. The idea is that this is browser-internal, so presumably it would still work even if JS from external sources is disabled.
No. The idea is that website authors do the work. The proposal suggests the browsers wholesale remove support and forget about it.
https://github.com/whatwg/html/issues/11523#issuecomment-315...
1 reply →