-
Notifications
You must be signed in to change notification settings - Fork 78
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
Provide XSLTProcessor #155
Comments
I've added this and a lot of other things which are implemented in one or more browsers in https://github.com/foolip/mdn-bcd-collector/tree/main/custom-idl. If there's a need for this non-standard IDL outside of mdn-bcd-collector, how about publishing it to a package similar to Putting it in webref would have certain benefits for maintaining it, but would also be a bit random. @dontcallmedom WDYT? |
I somehow have considered the DOM wiki page as a semi-spec and just parsed it as ReSpec (it works as it has |
I'm not sure, I don't think it belongs in browser-specs, but maybe it could be hacked in as an extra data source in Reffy? How about all the other non-standard IDL though, is that not interesting, is it just |
Others are not widely implemented, so far this is the only missing one in types-web not filtered out by BCD support data when I remove all local IDLs. |
given that I think the more general case of https://github.com/foolip/mdn-bcd-collector/tree/main/custom-idl would need more discussion - in particular, I don't think single-browser IDL customization should be added en masse to webref. |
Maybe we should just send a PR to DOM to add the interfaces and algorithms that are just TODOs, pushing the problem one level down. |
Or opening a WICG repo? 🤔 |
I added it to DOM in whatwg/dom#972 so it should reach webref soon. |
https://github.com/w3c/webref/blob/master/ed/idlnames/XSLTProcessor.idl is in, should make it to the package tomorrow |
https://wiki.whatwg.org/wiki/DOM_XSLTProcessor (whatwg/dom#181)
I think it's the only missing interface that doesn't belong to any real spec.
The text was updated successfully, but these errors were encountered: