23698 2013-11-01 08:59:25 +0000 Rename ParentNode to ContainerNode or some other unambiguous name 2013-11-04 11:18:02 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED WONTFIX P2 normal --- 1 rniwa annevk bugs ggaren mike www-dom public-webapps-bugzilla oldest_to_newest 95660 0 rniwa 2013-11-01 08:59:25 +0000 The name ParentNode is exceedingly confusing because we already have parentNode() on Node. Talking about the parentNode() of ParentNode, for example, will be very confusing. In WebKit/Blink, we use call it ContainerNode since it's a node that could contain other nodes. I'm open to other names but please disambiguate from other DOM class and method names. 95666 1 bugs 2013-11-01 11:12:24 +0000 Well, we have ChildNode too. So either call them ParentNode and ChildNode, or change both names. But, I think having Node.parentNode pointing to a ParentNode looks pretty good. 95668 2 annevk 2013-11-01 11:41:27 +0000 I would not know how to rename ChildNode. And I agree with Olli that the current names make a certain amount of sense. 95710 3 ggaren 2013-11-01 20:46:43 +0000 Is the value produced by Node.parentNode always of type ParentNode? 95711 4 ggaren 2013-11-01 21:20:43 +0000 > I would not know how to rename ChildNode. Let's not let a past bad naming decision justify a future bad naming decision. Or, as my mom likes to say, two wrongs don't make a right. 95736 5 rniwa 2013-11-03 00:56:42 +0000 Can't simply rename ChildNode to LeafNode? 95738 6 bugs 2013-11-03 17:49:12 +0000 ChildNode is not necessarily a leaf. 95758 7 annevk 2013-11-04 11:18:02 +0000 (In reply to Geoffrey Garen from comment #3) > Is the value produced by Node.parentNode always of type ParentNode? As far as I know, yes.