Re:Chrome intends to remove XSLT from the HTML spec
by zetafunction on Tuesday August 19, 2025 @02:24PM
(#44954627)
Disclaimer: I work on Chrome/Blink and I've also contributed a (very small) number of patches to libxml/libxslt.
It's not just a matter of replacing the libxslt; libxslt integrates quite closely with libxml2. There's a fair amount of glue to bolt libxml2/libxslt on to Blink (and WebKit); I can't speak for Gecko.
Even when there's no work on new XML/XSLT features, there's a passive cost to just having that glue code around since it adds quirks and special cases that otherwise wouldn't exist.
Re:Chrome intends to remove XSLT from the HTML spec
by cxr on Tuesday August 19, 2025 @07:40PM
(#44957284)
It's a bit strange that all the browser makers each has their own respective HTML parser, but when it comes to XML in particular they all rely on GNOME's implementation.
You'd think the actual number depending on the latter would be zero or one.
Re:Chrome intends to remove XSLT from the HTML spec
by MallocVoidstar on Tuesday August 19, 2025 @04:02PM
(#44955706)
> Xee implements modern versions of these specifications, rather than the versions released in 1999.
My understanding is that browsers specifically use the 1999 version and changing this would break compat
Re:Chrome intends to remove XSLT from the HTML spec
by colejohnson66 on Tuesday August 19, 2025 @07:12PM
(#44957114)
As if removing XSLT entirely won’t break back-compat?
[1] https://blog.startifact.com/posts/xee/
[2] https://github.com/Paligo/xee
[3] https://news.ycombinator.com/item?id=43502291