Re: [dom] Make Attr a Node again (#102)

So it sounds like we can reasonably assume that none of the 3 EventTarget methods are needed for compat. Having usage data would still be nice, of course.

The remaining uncertainty is all the remaining constants, attributes and methods of Node. For example `ownerDocument`, that does return the creating document. Someone just needs to go through all of these and think about which make *any* potential sense and which are simply useless and unlikely to be needed. `insertBefore()` is one method which has never done anything sensible and is unlikely to be needed.

In other news, chromestatus.com is back up, and is showing just 0.0002% for cloneNode:
https://www.chromestatus.com/metrics/feature/timeline/popularity/1034

I have been hesitant to just add everything from Node to Attr for measurement purposes, because that in itself carries *some* small risk, but I don't think there's any other way around it. @DigiTec, are you able to instrument this in Edge without making web-facing changes, or would you be willing to make the web-facing changes in order to measure it?

---
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/102#issuecomment-196647324