- From: <bugzilla@jessica.w3.org>
- Date: Mon, 18 Aug 2014 14:06:40 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26596 --- Comment #2 from Philip Jägenstedt <philipj@opera.com> --- 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? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 18 August 2014 14:06:43 UTC