27688 2014-12-23 21:53:26 +0000 Odd comment in DOM spec about the new "Elements" class 2015-07-15 06:49:15 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Linux RESOLVED FIXED P2 normal --- 1 xuzepa annevk d jackalmage mike www-dom public-webapps-bugzilla oldest_to_newest 116669 0 xuzepa 2014-12-23 21:53:26 +0000 https://dom.spec.whatwg.org/#collections:-elements [[ Elements is an ES6-style subclass of Array with two additional methods. It's the new NodeList / HTMLCollection. ]] How can a class named "Elements" legitimately replace the NodeList interface, when, in additions to Elements, a NodeList can also contain Text nodes and Comments etc? There are comments throughout the spec about "historical artifacts" that "we cannot rid the web of" and yet this seems like another one in the making... 116670 1 jackalmage 2014-12-23 22:55:11 +0000 The Elements class is for those functions that actually return only elements, like querySelectorAll and .childElements, etc. 120232 2 annevk 2015-05-08 09:19:19 +0000 It's interesting to consider whether perhaps we should give it a different name so it can in the future also be used for cases where we want to represent more than elements. Or whether we should restrict it to elements as the name suggests now... (And add a distinct class for nodes.) 122050 3 annevk 2015-07-15 06:49:15 +0000 If we need to represent nodes the methods don't make sense. We'd just use a simple Array for those cases. I did clarify the statement a bit to make that more clear: https://github.com/whatwg/dom/commit/96ef454f2f3326cf95b878b783a16a2dee16d4d3 Thanks for your input!