- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 10 Aug 2011 07:43:44 -0700
- To: Alan Gresley <alan@css-class.com>
- Cc: "L. David Baron" <dbaron@dbaron.org>, www-style@w3.org, Vitor Menezes <vmenezes@mozilla.com>
On Wed, Aug 10, 2011 at 3:12 AM, Alan Gresley <alan@css-class.com> wrote: > On 10/08/2011 12:29 PM, Tab Atkins Jr. wrote: >> On Tue, Aug 9, 2011 at 7:23 PM, Alan Gresley<alan@css-class.com> wrote: >>> I never liked this form of nesting. It does not occur in CSS3 >>> mediaqueries >>> nor any other syntax that has statements with blocks. I believe that >>> several >>> arguments appearing between blocks are better separated by commas or >>> keywords, like shown below for the ease of commenting parts out but more >>> so >>> to hunt down parsing errors. >>> >>> @supports not (display:block and display:inline) >>> >>> @supports not (display:block , display:inline) >> >> Neither of these work, as the property values may include commas or >> the keyword "and". > > Can you please give me examples of these? > > Off the top of my head, I can think of comma separated values for the > properties 'background' and 'box-shadow'. Apart from mediaqueries, where is > the keyword 'and' used? For example, the counter-reset property may reset a counter named "and". Similarly, the list-style property may set the type to a counter-style named "and" (from the Lists module). >> You absolutely must enclose the declarations in >> parens (or some other delimiter that cannot be mistaken for part of a >> value). > > OK, another possible delimiter. > > @supports (display:block) and ([display:inline]) > > @supports not ([display:block] and [display:inline]) > > @supports ([display:block]) I don't understand what problem you're trying to solve. ~TJ
Received on Wednesday, 10 August 2011 14:44:39 UTC