Re: Selector for parent/predecessor?

> ... such proposals get rejected because it doesn't fit the CSS processing
> model and also performance issues.

In most languages an author is aware of which operations are costly,
and which not, and can then make their own decisions. For example,
such selectors would not necessarily be so costly if the document was
small, or shallow.

CSS is quite a phenomena, since features seem to be regularly
"rejected" despite an obvious need, and so the author never gets the
chance to make a choice based on their own requirements.



Mark Birbeck
CEO Ltd.

t: +44 (0) 20 7689 9232

Download our XForms processor from

Received on Sunday, 20 August 2006 20:45:35 UTC