-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define XSLTProcessor #181
Comments
These are the surface-level differences between Gecko and Blink that I added as TODOs in our IDL file:
For the error handling, I think it probably doesn't matter much for compat if we return null or throw an exception. For parameter values, supporting any value type would be slightly more code, and since it's apparently not needed for compat I think just DOMString would be better. |
This is the use counter data for Chrome:
Both are so low that there's a good chance for some simplification if this is spec'd from scratch. |
See whatwg/dom#181 for details. PR: #738
Copied from https://wiki.whatwg.org/wiki/DOM_XSLTProcessor. Part of #181.
I've sent #972 to define just the I went ahead and queried HTTP Archive for "new XSLTProcessor" to see what current usage looks like, and put the results in https://gist.github.com/foolip/d59bd1ab27b2c93a1a37b434074ea410. It's "only" 7-8k sites, but my sense is that this is going to be found in more "enterprise-y" sites and that it's stuff nobody is around to maintain any longer. https://affiliates.skrill.com/includes/scripts/xmlxsl.js is a good example, where if that code is actually used (not checked) all modern browsers would go down the |
I also looked up sites that trigger Chrome's use counter, at looked at https://www.athome.co.jp/ as a sample. I did Since it seems relatively easy to find things that will break, I'm not very optimistic about getting rid of XSLT from the platform. I think at the very least a drop-in JavaScript implementation of |
Copied from https://wiki.whatwg.org/wiki/DOM_XSLTProcessor. Part of #181.
Since I formatted it nicely in web-platform-tests/wpt#28639, I'll repeat it here. Additional details on XSLT in HTML:
|
See https://wiki.whatwg.org/wiki/DOM_XSLTProcessor. Per whatwg/html#738 this is implemented in all browsers now.
The text was updated successfully, but these errors were encountered: