W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2006

[whatwg] getElementsByClassName()

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 6 Feb 2006 22:29:32 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0602062227010.2856@dhalsim.dreamhost.com>
On Mon, 6 Feb 2006, Brad Fults wrote:
>
> On 2/5/06, Ian Hickson <ian at hixie.ch> wrote:
> > I can certainly see myself speccing a getElementsBySelector() API as part
> > of Selectors 2. But either way, the spec for gEBS is simple; it returns
> > the same type as getElementsByTagName(), it is accessible from Document
> > and Element nodes and selects a subset of the descendants of that node, it
> > takes a single argument (a string representing a selector), its first
> > version doesn't support namespaces, and it raises an exception SYNTAX_ERR
> > if the string can't be successfully parsed by the UA.
> 
> [...]
> 
> What will it take to kick start the process for getElementsBySelector()? 
> I suppose a few browser implementations would be good fuel.

If you can get two browsers to interoperably implement the spec above, and 
then provide test cases to show this, then it'll increase the pressure on 
the CSSWG to get on with writing a spec for it. If you can get the two 
implementations to happen in the next month or so, then I might even be 
able to slide it into the Selectors 1 specification (no guarentees, but if 
there are two implementations in makes it easier)...

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 6 February 2006 14:29:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:26 UTC