Re: [whatwg/dom] Define XSLTProcessor (#181)

I also looked up [sites that trigger Chrome's use counter](https://gist.github.com/foolip/617b49d9f53a20c15fe1d75141bf679d), at looked at https://www.athome.co.jp/ as a sample. I did `delete window.XSLTProcessor` and the result at the bottom of the page is:
![image](https://user-images.githubusercontent.com/498917/114998867-a4fe8900-9ea1-11eb-88b0-e73ea9523623.png)

But it should look like this:
![image](https://user-images.githubusercontent.com/498917/114999006-c2335780-9ea1-11eb-9721-dc2ad1807ea0.png)

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 `XSLTProcessor` would be needed to help people transition, and that's a lot of work...

-- 
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-821027856