Ah, I think I see now. You don't want the nextElementSibling API to _return_ non-elements, you just want the nextElementSibling to be available on all nodes so that no matter where you land in the DOM, you can always get to the next element. Gotcha.
-----Original Message----- From: Daniel Glazman [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 10:05 AM To: Travis Leithead Cc: [EMAIL PROTECTED]; Webapps Subject: Re: comment on Element Traversal Spec Travis Leithead wrote: > I thought that Node.nextSibling / previousSibling work this way? Isn't the > whole reason for ElementTraversal to explicitly do element navigation only (a > use case that nextSibling/previousSibling made more complicated for web > developers)? Having nextElementSibling available on Text and other nodes will provide a great replacement for a code chunk the whole web and JS chrome is full of : while (node && node.nodeType != Node.ELEMENT_NODE) node = node.nextSibling; </Daniel>
