- From: David Baron via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 06 Jun 2011 17:49:10 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-conditional In directory hutz:/tmp/cvs-serv32507 Modified Files: Overview.html Overview.src.html Log Message: Write the illegal example I wanted for @supports. Index: Overview.html =================================================================== RCS file: /sources/public/csswg/css3-conditional/Overview.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -d -r1.7 -r1.8 --- Overview.html 6 Jun 2011 17:07:30 -0000 1.7 +++ Overview.html 6 Jun 2011 17:49:08 -0000 1.8 @@ -639,11 +639,39 @@ }</pre> </div> - <p>To avoid confusion between and and or, the syntax requires that both and - and or be specified explicitly (rather than, say, using commas or spaces - for one of them). Likewise, to avoid confusion caused by precedence rules, - the syntax does not allow and, or, and not operators to be mixed without a - layer of parentheses. <span class=issue>Add examples.</span> + <p>To avoid confusion between ‘<code class=css>and</code>’ and + ‘<code class=css>or</code>’, the syntax requires that both + ‘<code class=css>and</code>’ and ‘<code + class=css>or</code>’ be specified explicitly (rather than, say, + using commas or spaces for one of them). Likewise, to avoid confusion + caused by precedence rules, the syntax does not allow ‘<code + class=css>and</code>’, ‘<code class=css>or</code>’, and + ‘<code class=css>not</code>’ operators to be mixed without a + layer of parentheses. + + <div class=example> + <p>For example, the following rule is not valid: + + <pre class=illegal-example>@supports (transition-property: color) or + (animation-name: foo) and + (transform: rotate(10deg)) { + // ... +}</pre> + + <p>Instead, authors must write one of the following:</p> + + <pre>@supports ((transition-property: color) or + (animation-name: foo)) and + (transform: rotate(10deg)) { + // ... +}</pre> + + <pre>@supports (transition-property: color) or + ((animation-name: foo)) and + (transform: rotate(10deg))) { + // ... +}</pre> + </div> <h2 id=at-document><span class=secno>6. </span>Document queries: the ‘<code class=css>@document</code>’ rule</h2> Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/css3-conditional/Overview.src.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -d -r1.7 -r1.8 --- Overview.src.html 6 Jun 2011 17:07:30 -0000 1.7 +++ Overview.src.html 6 Jun 2011 17:49:08 -0000 1.8 @@ -457,13 +457,31 @@ } }</pre></div> -<p>To avoid confusion between and and or, the syntax requires that both -and and or be specified explicitly (rather than, say, using commas or -spaces for one of them). Likewise, to avoid confusion caused by -precedence rules, the syntax does not allow and, or, and not operators -to be mixed without a layer of parentheses. <span class="issue">Add -examples.</span></p> +<p>To avoid confusion between ''and'' and ''or'', the syntax requires +that both ''and'' and ''or'' be specified explicitly (rather than, say, +using commas or spaces for one of them). Likewise, to avoid confusion +caused by precedence rules, the syntax does not allow ''and'', ''or'', +and ''not'' operators to be mixed without a layer of parentheses.</p> +<div class="example"> +<p>For example, the following rule is not valid: +<pre class="illegal-example">@supports (transition-property: color) or + (animation-name: foo) and + (transform: rotate(10deg)) { + // ... +}</pre> +<p>Instead, authors must write one of the following:</p> +<pre>@supports ((transition-property: color) or + (animation-name: foo)) and + (transform: rotate(10deg)) { + // ... +}</pre> +<pre>@supports (transition-property: color) or + ((animation-name: foo)) and + (transform: rotate(10deg))) { + // ... +}</pre> +</div> <h2 id="at-document">Document queries: the '@document' rule</h2>
Received on Monday, 6 June 2011 17:49:11 UTC