W3C home > Mailing lists > Public > www-style@w3.org > September 2010

Re: Enhancing grouping of selectors

From: Paul Duffin <pduffin@volantis.com>
Date: Sat, 18 Sep 2010 02:26:08 -0600 (MDT)
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "L. David Baron" <dbaron@dbaron.org>, Matthew Millar <mattmill30@hotmail.com>, www-style@w3.org
Message-ID: <1881690790.18909.1284798368495.JavaMail.root@zimbra.volantis.com>

----- Original Message -----
> (Note, though, that you wrote the selector wrong. :any()'s arguments
> are comma-separated, because you can have arbitrary selectors as
> arguments. So it needs to be:
> :any(e, #id, .class) :any(e, #id, .class) :any(e, #id, .class) {...}

Ok, I couldn't find :any defined anywhere, ,only http://dbaron.org/log/20100424-any which only allows a simple selector in the :any(). Is that just an implementation limitation?

On a related note I just looked at :not(), http://www.w3.org/TR/css3-selectors/#negation, which is a similar 'logical pseudo class' and it is limited to a simple selector, and cannot contain itself. What are the reasons for this limitation, e.g. why can't I write any of the following?
* :not(a.special)
* :not(li > a)
* :not(ol > li, ul > li)

The latter could be written as:
* :not(:any(ol, ul) > li)
Received on Saturday, 18 September 2010 08:26:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:49:47 UTC