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

Re: [css3-selectors] Grouping

From: Brad Kemper <brad.kemper@gmail.com>
Date: Fri, 8 Jan 2010 10:05:41 -0800
Cc: Nikita Popov <privat@ni-po.com>, news <news@terrainformatica.com>, www-style list <www-style@w3.org>
Message-Id: <44D4EB9E-13AF-47ED-9DBF-63CCF3C1E6E5@gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

On Jan 8, 2010, at 9:55 AM, Tab Atkins Jr. wrote:

> On Fri, Jan 8, 2010 at 11:33 AM, Nikita Popov <privat@ni-po.com> wrote:
>> I think that the variant with brackets I proposed is little bit better,
>> because it  could  be more widely used, e.g.
>> input([type=submit], [type=number], ...)
>> ("could" because I don't know, whether something like this, would be
>> good...)
> 
> There's still no need to extend the syntax there.  You can do that
> with the pseudoclass:
> 
> input:any([type=submit],[type=number]) {}
> 
> I don't think there's anything you could do with parens in selectors
> that wouldn't be possible with the pseudoclass.  As well, you stay
> within existing syntax, which means we don't have to change the
> grammar and possibly introduce new bugs.

I really like the idea in general, but I'm not sure about it being a pseudo-class. I'm not against that at this point, mind you, but it is not obvious to me if the following two rules are equivalent:

div :any(span,div)
div:any(span,div)

or would that second version be nonsense, and simple selectors as arguments could only be used with a universal selector (or naked, implying a universal selector there). 

Received on Friday, 8 January 2010 18:06:18 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:23 GMT