[no subject]

[...]

> >As of the pseudo-class selection, yes some more code is needed to
> >handle them, even if not all of them will be easy to support.
> >Do not hesitate to ask if you want them to be supported. We will
> >start a discussion about it.
> 
> I do believe ':first-child' should be handled. I don't understand
> why you say it is dynamic. From my understanding 'dynamic' means
> 'as a result of user interaction', i.e. things like 'hover' and
> other elements that require more than just the statically available
> information. 'first-child', however, is strictly structural, i.e.
> you can know it from the topology of the tree. It's no different
> from the 'A + B' selector, no ?

You are totaly right. I was a bit confused here.
What I wanted to say is that *some* of the 
pseudo:class types of selector where "dynamic" like hover etc ...
In that case, implementing them needs some more "infrastructure".
During the first implementation of selectors, I decided just to
ignore the pseudo-classes type of selectors for the sake of
simplicity. I thought I would come back to this later.
Obviously, I forgot the :first-child case.
As it seems it is needed, I will work on its implementation then.

Best wishes,

Dodji.

ps: the A + B patch is commited and should appears in the
anoncvs after the lag period.