ISSUE-6
Element Traversal Nodelist
Should the ElementTraversal Interface Have a Nodelist?
- State:
- CLOSED
- Product:
- Element Traversal
- Raised by:
- Doug Schepers
- Opened on:
- 2008-06-17
- Description:
Daniel Glazman requested that a nodelist or item accessor be added to the ET spec, in <http://lists.w3.org/Archives/Public/public-webapi/2008Mar/0226.html>, spawning a long thread. Doug discussed the history of similar proposals, from himself, Mozilla, and others in <http://lists.w3.org/Archives/Public/public-webapi/2008Mar/0246.html>. On the plus side, it would allow for discrete access to elements in some use cases, and would be easy to implement for UAs that already have a nodelist implementation. On the downside, it is heavier to implement if the UA doesn't already have nodelist (such as some mobile uses), and ET is already referenced by other specifications.
- Related Actions Items:
- No related actions
- Related emails:
- Re: Element Nodelist - ISSUE-6 (was: ElementTraversal progress?) (from jresig@mozilla.com on 2008-07-07)
- Re: Element Nodelist - ISSUE-6 (was: ElementTraversal progress?) (from jonas@sicking.cc on 2008-07-06)
- Re: Element Nodelist - ISSUE-6 (was: ElementTraversal progress?) (from jresig@mozilla.com on 2008-07-06)
- Re: Element Nodelist - ISSUE-6 (from daniel.glazman@disruptive-innovations.com on 2008-06-24)
- Re: Element Nodelist - ISSUE-6 (from jonas@sicking.cc on 2008-06-23)
- Element Nodelist - ISSUE-6 (was: ElementTraversal progress?) (from schepers@w3.org on 2008-06-23)
- Re: ISSUE-6 (Element Traversal Nodelist): Should the ElementTraversal Interface Have a Nodelist? [Element Traversal] (from jonas@sicking.cc on 2008-06-17)
- ISSUE-6 (Element Traversal Nodelist): Should the ElementTraversal Interface Have a Nodelist? [Element Traversal] (from sysbot+tracker@w3.org on 2008-06-17)
Related notes:
2008-06-17 06:15:23: http://lists.w3.org/Archives/Public/public-webapi/2008May/0490.html
[Doug Schepers]
2008-06-17 06:15:29: http://lists.w3.org/Archives/Public/public-webapi/2008Jun/0000.html [Doug Schepers]
2008-06-17 06:19:41: After discussing with various folks (including mobile implementors, the JSR folks, and the SVG WG), I propose that we leave Element Traversal as is, since it is indeed intended to be a traversal interface, and create a new complementary spec, Element Nodelist, which provides a nodelist interface for Elements. It can be implemented easily in a complementary manner, and ET's "childElementCount" attribute can simply alias the ElementNodelist interface's "length" attribute. [Doug Schepers]
2008-06-25 07:28:40: RESOLVED: No, will create separate spec for Element NodeList. [Doug Schepers]
Changelog:
2008-06-17 06:13:25: Created issue 'Should the ElementTraversal Interface Have a Nodelist?' nickname Element Traversal Nodelist owned by Doug Schepers on product Element Traversal, description 'Daniel Glazman requested that a nodelist or item accessor be added to the ET spec, in <http://lists.w3.org/Archives/Public/public-webapi/2008Mar/0226.html>, spawning a long thread. Doug discussed the history of similar proposals, from himself, Mozilla, and others in <http://lists.w3.org/Archives/Public/public-webapi/2008Mar/0246.html>. On the plus side, it would allow for discrete access to elements in some use cases, and would be easy to implement for UAs that already have a nodelist implementation. On the downside, it is heavier to implement if the UA doesn't already have nodelist (such as some mobile uses), and ET is already referenced by other specifications. ' non-public [Doug Schepers]
2008-06-17 20:39:49: Status changed to 'pending review' [Doug Schepers]
2008-06-25 07:28:40: Status changed to 'closed' [Doug Schepers]