@@ -639,11 +639,39 @@ <h2 id=at-supports><span class=secno>5. </span>Feature queries: the
639639}</ pre >
640640 </ div >
641641
642- < p > To avoid confusion between and and or, the syntax requires that both and
643- and or be specified explicitly (rather than, say, using commas or spaces
644- for one of them). Likewise, to avoid confusion caused by precedence rules,
645- the syntax does not allow and, or, and not operators to be mixed without a
646- layer of parentheses. < span class =issue > Add examples.</ span >
642+ < p > To avoid confusion between ‘< code class =css > and</ code > ’ and
643+ ‘< code class =css > or</ code > ’, the syntax requires that both
644+ ‘< code class =css > and</ code > ’ and ‘< code
645+ class =css > or</ code > ’ be specified explicitly (rather than, say,
646+ using commas or spaces for one of them). Likewise, to avoid confusion
647+ caused by precedence rules, the syntax does not allow ‘< code
648+ class =css > and</ code > ’, ‘< code class =css > or</ code > ’, and
649+ ‘< code class =css > not</ code > ’ operators to be mixed without a
650+ layer of parentheses.
651+
652+ < div class =example >
653+ < p > For example, the following rule is not valid:
654+
655+ < pre class =illegal-example > @supports (transition-property: color) or
656+ (animation-name: foo) and
657+ (transform: rotate(10deg)) {
658+ // ...
659+ }</ pre >
660+
661+ < p > Instead, authors must write one of the following:</ p >
662+
663+ < pre > @supports ((transition-property: color) or
664+ (animation-name: foo)) and
665+ (transform: rotate(10deg)) {
666+ // ...
667+ }</ pre >
668+
669+ < pre > @supports (transition-property: color) or
670+ ((animation-name: foo)) and
671+ (transform: rotate(10deg))) {
672+ // ...
673+ }</ pre >
674+ </ div >
647675
648676 < h2 id =at-document > < span class =secno > 6. </ span > Document queries: the
649677 ‘< code class =css > @document</ code > ’ rule</ h2 >
0 commit comments