W3C home > Mailing lists > Public > www-style@w3.org > August 2006

Re: Selector for parent/predecessor?

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Sun, 20 Aug 2006 21:45:23 +0100
Message-ID: <640dd5060608201345m671df91bv4a9d3fc9a272507@mail.gmail.com>
To: www-style@w3.org

> ... 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.

Regards,

Mark

-- 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
http://www.formsPlayer.com/
Received on Sunday, 20 August 2006 20:45:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:46 GMT