jim.ley at gmail.com
Sat Jan 14 09:35:13 PST 2006
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.
More information about the whatwg