Thank you for moz-any(), Mozilla!

I hope Google Chrome / WebKit will implement it soon as well so I can use it in my webapp. (For IE I’ll be using Chrome Frame.)

Magne Andersson:
cycle() will be useful indeed! +1.

Thanks, great work (as always), but there’s one point…

> First, it’s just a proposal, and hasn’t made its way into any specification.
> And second, it isn’t quite ready for prime-time, though, since it doesn’t yet
> handle specificity correctly.

I wonder if these are real reasons for it to have a -moz- prefix? Compare

/* Level 2 */
section section h1, section article h1, section aside h1, section nav h1,
article section h1, article article h1, article aside h1, article nav h1,
aside section h1, aside article h1, aside aside h1, aside nav h1,
nav section h1, nav article h1, nav aside h1, nav nav h1, {
font-size: 20px;
}

with

/* Level 2 */
-moz-any(section, article, aside, nav)
-moz-any(section, article, aside, nav) h1,
-webkit-any(section, article, aside, nav)
-webkit-any(section, article, aside, nav) h1,
-o-any(section, article, aside, nav)
-o-any(section, article, aside, nav) h1 {
font-size: 20px;
}

Yes, second is still shorter, but you know what I mean. I agree the prefix is useful for something like gradients, where different interpretations and different syntaxes are possible, but here — isn’t it redundant?

1. voracity

   It would be great if you do the equivalent of “:any” on vendor prefixes. For example:

   /* Level 2 */
   -[moz,webkit,o,none]-any(section, article, aside, nav)
   -[moz,webkit,o,none]-any(section, article, aside, nav) h1 {
   font-size: 20px;
   }

   This would make life so much easier for a whole heap of things…

   May 19th, 2010 at 04:52
   1. voracity

      Actually, extending this idea slightly:

      .box {
      border-[left,top]: white 1px solid;
      border-[right,bottom]: black 1px solid;
      }

      May 19th, 2010 at 04:56
      1. CyberSkull

         I like your idea! That would simplify so many definitions! :D

         July 7th, 2010 at 22:11

2. Magne Andersson

   The prefix is required until a spec has reached Candidate Recommendation status, per CSS WG. We must have it on affected properties.

   May 19th, 2010 at 08:23
   1. zoe somebody

      While working on implementing a new HTML5 default markup scheme I discovered the Firefox UA stylesheet is already actually using the any() selector to adjust the size of h1 tags nested in html5 sectioning container as posited in the article above (from html.css):

      h3, *:-moz-any(article, aside, nav, section) *:-moz-any(article, aside, nav, section) h1 { display: block; font-size: 1.17em; font-weight: bold; margin: 1em 0; }

      While testing my markup scheme before styling anything I discovered that the h1 tags were not all the same size in FF vs every other browser. Inded, the nested h1’s were being sized down to h3’s and h4’s.

      While I for one really appreciate the any() selector and would like to use it for this very reason, implementing this in the UA stylesheet is unfortunate because now it is yet another thing that needs normalized for between browsers.

      I would push for the any() selector to become a part of the spec, but I would NOT like any extra formatting applied by the browsers until that extra formatting is standardized.

      Just thought I would post this here since this was the first search that came up as I started figuring this out.

      August 28th, 2011 at 22:43
      1. Paul Rouget

         This is not any extra formatting. This is part of the spec (nested headers are smaller). The fact we use :-moz-any doesn’t change anything. We could have used a more complex selector to achieve the same thing.

         August 29th, 2011 at 02:24