26596 2014-08-18 12:09:13 +0000 Attr.value cannot be readonly 2014-08-18 14:21:26 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Linux RESOLVED FIXED P2 normal --- 1 philipj annevk bugs crimsteam jonas justinut2010 mike Ms2ger www-dom public-webapps-bugzilla oldest_to_newest 110227 0 philipj 2014-08-18 12:09:13 +0000 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 110231 1 annevk 2014-08-18 13:33:49 +0000 Also need to add Attr.prototype.textContent as alias per http://www.chromestatus.com/metrics/feature/timeline/popularity/349 110232 2 philipj 2014-08-18 14:06:40 +0000 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? 110234 3 annevk 2014-08-18 14:13:52 +0000 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. 110236 4 annevk 2014-08-18 14:17:38 +0000 *** Bug 25086 has been marked as a duplicate of this bug. *** 110240 5 annevk 2014-08-18 14:21:26 +0000 https://github.com/whatwg/dom/commit/f64b0c82896d68ad534544ed8109ac41c175840d