W3C home > Mailing lists > Public > public-webapi@w3.org > April 2008

Re: [Element Traversal LC] access to element by index

From: Simon Pieters <simonp@opera.com>
Date: Fri, 04 Apr 2008 00:19:12 +0200
To: "Jonas Sicking" <jonas@sicking.cc>, "Bjoern Hoehrmann" <derhoermi@gmx.net>
Cc: "Daniel Glazman" <daniel.glazman@disruptive-innovations.com>, "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.t812ya2kidj3kv@hp-a0a83fcd39d2.belkin>

On Thu, 03 Apr 2008 19:04:55 +0200, Jonas Sicking <jonas@sicking.cc> wrote:

> Ah, thanks, that does explain the issue.
>
> Though I think that if we want the web to have a .childElements NodeList  
> available then we have two options:
> 1. Add it to the ElementTraversal spec and have SVG Tiny say that they  
> no longer require the full ElementTraversal spec.
> 2. Add it to a separate unrelated spec, such as HTML5.
>
> Result 2 doesn't seem any better than 1. The end result for both is that  
> SVG tiny only require a certain set of properties, and with 2 we'd have  
> to wait some undefined amount of time before getting it into an Rec,  
> possibly of a spec that will have a much slower adoption rate.

The result of (2) probably also means that there's both childElementCount  
and childElements.length to do the same.

-- 
Simon Pieters
Opera Software
Received on Thursday, 3 April 2008 22:20:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 April 2008 22:20:20 GMT