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

[whatwg] getElementsByCSSSelector

From: Julien Couvreur <julien.couvreur@gmail.com>
Date: Sat, 14 Jan 2006 09:28:00 -0800
Message-ID: <919035ab0601140928i60aa55b2m9eaed99ac2351088@mail.gmail.com>
One of the main uses is to bind behaviors to elements. This allows for
a clean markup with a well separated logic.

The Behaviour library takes that approach:
http://bennolan.com/behaviour/

Cheers,
Julien

On 1/14/06, Jim Ley <jim.ley at gmail.com> wrote:
> On 1/14/06, Karoly Negyesi <karoly at negyesi.net> wrote:
> > A getElementsByCSSSelector IMO would be great and introduces minimal plus
> > burden on browsers -- they have CSS selector code anyways.
> >
> > It's very unfriendly that I can do magic with CSS2/3 selectors and then I
> > need to translate them myself if I want to change them on-the-fly.
>
> Why would you want to change the content of all elements that matched
> a particular selector?
>
> Could you explain some use cases?
>
> Jim.
>
Received on Saturday, 14 January 2006 09:28:00 UTC

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