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

If making Attr to not inherit from Node is still considered (even in the long term), then having usage of `cloneNode()` may be useful in future, because someone reported the potential problem with its absence for Attr. At now I see some data for:
Attr.nodeValue https://www.chromestatus.com/metrics/feature/timeline/popularity/348
Attr.textContent https://www.chromestatus.com/metrics/feature/timeline/popularity/349
Attr.specified https://www.chromestatus.com/metrics/feature/timeline/popularity/162
Attr.ownerElement https://www.chromestatus.com/metrics/feature/timeline/popularity/160
With more data you don't have to wait another few weeks/months to take next decisions around Attr, like placing equivalent of 'cloneNode()' directly in the Attr (if we really need them). But the basic question is: if anyone really considering making Attr a non-Node, at least as an experiment in most recent version of engine? After few years this is still just a idea (excluding Servo), but somehow received a recommendation (http://www.w3.org/TR/dom/)... perhaps too early (this only creates confusion)...

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/102#issuecomment-159678437