This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.chromestatus.com/metrics/feature/timeline/popularity/299 http://www.chromestatus.com/metrics/feature/timeline/popularity/303 The use counters for the setter are a bit too high, even if only counting when actually attached to an element. :( Background: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21986#c9
Also need to add Attr.prototype.textContent as alias per http://www.chromestatus.com/metrics/feature/timeline/popularity/349
First I think we should determine if making Attr not inherit Node and not have child nodes is going to fly. Unfortunately there are lots of APIs that expose the fact that Attr is a Node and has children, at least: childNodes firstChild lastChild insertBefore replaceChild removeChild appendChild hasChildNodes cloneNode normalize contains ... and probably more. The best I can think of is to try to separate these into buckets AttrChildNodeAccess and AttrChildNodeModification and see if usage is low enough. Am I missing something?
That seems correct. Whether Attr needs to be a Node we should probably track separately from whether Attr should have a settable value and textContent though. Would be really sad if that was required.
*** Bug 25086 has been marked as a duplicate of this bug. ***
https://github.com/whatwg/dom/commit/f64b0c82896d68ad534544ed8109ac41c175840d