Viewing profile — dev0001

At the moment, XSLT in a browser doesn't depend on Javascript, so works even if JS is turned off. Using a polyfill instead will mean that XSLT will only work if JS is turned on.

Saxonica is an Employee Ownership Trust and the team as a whole is relatively young (far off from retirement). "Saxonica today counts some of the world's largest companies among it…

Not really, because that would add a dependency on Javascript whereas, at the moment, XSLT works without Javascript enabled.

The vast majority of feedback on the GitHub issue was respectful — unless you consider opposing the proposal disrespectful.

The vulnerabilities associated with native client-side XSLT are not in the language itself (XSLT 1.0) but instead are caused by bugs in the browser implementations. Ps. The XSLT la…

Would you say the same about CSS if browsers only supported version 1.0 while it was being used in many other contexts and version 4.0 was being worked on?

Most of the time you wouldn't even notice that a web page is the result of a client-side XSLT transformation, for example: https://xmpp.org/extensions/xep-0182.xml

U.S. legislation is delivered on the web as XSLT-styled XML and depends on web browsers continuing to provide native support for client-side XSLT. Examples: https://www.congress.go…

> the hate towards people who actually made the web happen (Smaug, Anne, Emilo, etc…) The vast majority of comments on https://github.com/whatwg/html/issues/11523 are polite and re…

From the GitHub thread ( https://github.com/whatwg/html/issues/11523#issuecomment-315... ) > I don't think there's a strong "Open Web" argument to be made here. XML data files bein…