27623 2014-12-16 06:44:04 +0000 A node.index() method for the ChildNode interface? 2014-12-16 15:54:23 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED WORKSFORME P2 normal --- 1 hey.hgl annevk donjjordan mike www-dom zcorpan public-webapps-bugzilla oldest_to_newest 116366 0 hey.hgl 2014-12-16 06:44:04 +0000 Love the jquery-like ChildNode interface. I wonder if it makes sense to add a node.index() method that returns the node's index. This would be very helpful when dealing with DOM ranges: range.setStart(node.parentNode, node.index()) 116367 1 zcorpan 2014-12-16 07:47:45 +0000 Alternatively maybe we could tweak the APIs that use indexes as input to also allow nodes as input: range.setStart(node.parentNode, node) 116368 2 zcorpan 2014-12-16 07:48:58 +0000 Or range.setStart(node) 116369 3 hey.hgl 2014-12-16 07:52:04 +0000 This probably won't cut it, since sometimes range.setEnd(node.parentNode, node.index() + 1); // or +2 is needed 116370 4 hey.hgl 2014-12-16 08:12:38 +0000 It turns out we already have setStartBefore and the likes, which does exactly what Simon suggest. I personally have no use for this method for now. Not sure if should close the bug. 116384 5 donjjordan 2014-12-16 15:54:23 +0000 Since a node.index() function is required by many of the DOM's internal algorithms (i.e. https://dom.spec.whatwg.org/#concept-tree-index), all of the DOM implementations already have a privately-defined method like this. If a use is ever found for this function outside of what is already provided by the DOM, then node.index() would be a freebie to expose in the IDL. For now, there is no point in cluttering up the API.