- From: Philip Jägenstedt <notifications@github.com>
- Date: Fri, 16 Apr 2021 01:37:54 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 April 2021 08:38:06 UTC
I've sent https://github.com/whatwg/dom/pull/972 to define just the `XSLTProcessor` interface, pointing back to this issue. 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 `TransformXML_Moz` path and break at the `new XSLTProcessor()` call. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/181#issuecomment-821018175
Received on Friday, 16 April 2021 08:38:06 UTC