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

[whatwg] getElementsByCSSSelector

From: Jim Ley <jim.ley@gmail.com>
Date: Sat, 14 Jan 2006 17:35:13 +0000
Message-ID: <851c8d310601140935s33b25dbcwc481ea4ed12a9714@mail.gmail.com>
On 1/14/06, Julien Couvreur <julien.couvreur at gmail.com> wrote:

[use cases for CSS selectors]
> One of the main uses is to bind behaviors to elements. This allows for
> a clean markup with a well separated logic.

Then it fails miserably at the job,  HTML documents render
progressively, behaviour also needs to render progressively,
getElementsByCSSSelector fails at this.

There could indeed be useful methods for achieving this functionality
sort of thing - for example something along the line of events bound
at the css selector level, something like -
cssSelectorAddEventListener(".chicken td","DOMActivate", ...) maybe?
but your proposed DOM method fails to meet your described use case -
do you have any others, some that actually succeed, rather than being
a half way measure based on current practices that are stuck due to
the limited nature.

Received on Saturday, 14 January 2006 09:35:13 UTC

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