16409 2012-03-16 20:54:00 +0000 DOM4: Consider LeafNode interface which Node inherits from 2012-05-15 10:53:55 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED WONTFIX P2 enhancement --- 1 ajvincent annevk bzbarsky mike www-dom public-webapps-bugzilla oldest_to_newest 65676 0 ajvincent 2012-03-16 20:54:00 +0000 Andreas Gal's domjs project ( https://github.com/andreasgal/dom.js ) has an interesting idea: a separate class for "leaf nodes", which cannot have children. I wonder if this might be worth adding to the DOM4 spec, by splitting the Node interface into two parts: (1) A LeafNode interface which implements all the current Node's interface properties except firstChild, childNodes, lastChild, insertBefore, appendChild, replaceChild, and removeChild. (2) A Node interface which inherits from LeafNode and adds those extracted properties. interface LeafNode : EventTarget; interface Node : LeafNode; It might make text nodes, comments, etc. - nodes that can't have children - somewhat simpler. I'm only asking for consideration of the idea. 65678 1 bzbarsky 2012-03-16 21:18:54 +0000 Wouldn't this break existing scripts that iterate over the DOM? How do you expect UAs to implement it? 65749 2 annevk 2012-03-19 16:04:23 +0000 We have followed this approach for new mutation methods. Not sure if we can do it for the legacy ones. 65750 3 annevk 2012-03-19 16:05:06 +0000 If you want to do this I suggest experimenting in a browser whether you can move some methods down from Node and then remove them from selected interfaces. 67722 4 annevk 2012-05-15 10:53:55 +0000 Resolving as WONTFIX because changing the classes around is a huge compatibility risk. If a browser (like with the Attr redesign) is willing to test this out we'll look at this more concretely.