News for hackers. Stuff that matters.
Re:Chrome intends to remove XSLT from the HTML spec by webstrand on Tuesday August 19, 2025 @12:50PM (#44953588)
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.
Re:Chrome intends to remove XSLT from the HTML spec by NoGravitas on Tuesday August 19, 2025 @01:16PM (#44953877)
This is clearly the Right Thing. So what do you suppose the chance of it happening is?
Re:Chrome intends to remove XSLT from the HTML spec by bilog on Tuesday August 19, 2025 @05:39PM (#44956510)
There's even a JS implementation of XSLT 3.0 already (SaxonJS).
Re:Chrome intends to remove XSLT from the HTML spec by webstrand on Tuesday August 19, 2025 @05:52PM (#44956610)
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.
Re:Chrome intends to remove XSLT from the HTML spec by dev0001 on Wednesday August 20, 2025 @02:06AM (#44959091)
Not really, because that would add a dependency on Javascript whereas, at the moment, XSLT works without Javascript enabled.
Re:Chrome intends to remove XSLT from the HTML spec by dpassens on Wednesday August 20, 2025 @07:00AM (#44960715)
Not necessarily. The idea is that this is browser-internal, so presumably it would still work even if JS from external sources is disabled.
Re:Chrome intends to remove XSLT from the HTML spec by colejohnson66 on Thursday August 21, 2025 @09:36AM (#44972620)
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...

Re:Chrome intends to remove XSLT from the HTML spec by dpassens on Thursday August 21, 2025 @11:58AM (#44974360)
Oh, I understand that that's the WHATWG proposal. I'm talking about webstrand's idea.