Changed 'invalid variable use' to 'invalid at computed-value time' and rephrased a few bits to be more general, since attr() probably needs to do the same thing.

Author: tabatkins

css-variables/Overview.html

@@ -36,14 +36,14 @@
 
    <h1>CSS Variables Module Level 1</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 28 September
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 September
     2011</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://www.w3.org/TR/2011/ED-css-variables-20110928/">http://dev.w3.org/csswg/css-variables/</a>
+     href="http://www.w3.org/TR/2011/ED-css-variables-20110929/">http://dev.w3.org/csswg/css-variables/</a>
      <!--<dt>Latest version:
 		<dd><a href="http://www.w3.org/TR/css-variables/">http://www.w3.org/TR/css-variables/</a>-->
 
@@ -353,9 +353,10 @@ <h2 id=using-variables><span class=secno>3. </span> Using Variables</h2>
    value that nonetheless has no relation to the variable of that name.
 
   <p>A variable is substituted for its value in the property value at
-   computed-value time. If the property value, once all variables are
-   substituted in, is invalid for the property, that is an <a
-   href="#invalid-variable-use"><i>invalid variable use</i></a>.
+   computed-value time. If a declaration, once all variables are substituted
+   in, is invalid, the declaration is <a
+   href="#invalid-at-computed-value-time"><i>invalid at computed-value
+   time</i></a>.
 
   <div class=example>
    <p>For example, the following usage is fine from a syntax standpoint, but
@@ -378,14 +379,17 @@ <h3 id=using-invalid-variables><span class=secno>3.1. </span> Using Invalid
   <p>An <dfn id=invalid-variable title="invalid variable|invalid
    variables">invalid variable</dfn> results from having variables directly
    or indirectly refer to themselves, or from using an undefined variable.
-   Using an <a href="#invalid-variable"><i>invalid variable</i></a> results
-   in an <a href="#invalid-variable-use"><i>invalid variable use</i></a>.
-
-  <p>An <dfn id=invalid-variable-use>invalid variable use</dfn> results from
-   either using an <a href="#invalid-variable"><i>invalid variable</i></a> in
-   a property value, or using a valid variable that produces an invalid
-   property value when it is substituted in. When this happens, the property
-   the variable is used in must compute to the property's initial value.
+   Using an <a href="#invalid-variable"><i>invalid variable</i></a> in a
+   property value makes the declaration <a
+   href="#invalid-at-computed-value-time"><i>invalid at computed-value
+   time</i></a>.
+
+  <p>A declaration that is <dfn id=invalid-at-computed-value-time>invalid at
+   computed-value time</dfn> results from either using an <a
+   href="#invalid-variable"><i>invalid variable</i></a> in a property value,
+   or using a valid variable that produces an invalid declaration when it is
+   substituted in. When this happens, the declaration must compute to the
+   property's initial value.
 
   <div class=example>
    <p>For example, in the following code:</p>
@@ -397,13 +401,15 @@ <h3 id=using-invalid-variables><span class=secno>3.1. </span> Using Invalid
 
    <p>the &lt;p> elements will have transparent backgrounds (the initial
     value for &lsquo;<code class=property>background-color</code>&rsquo;),
-    rather than red backgrounds.</p>
+    rather than red backgrounds. This is different from the second</p>
   </div>
 
-  <p class=note>The <a href="#invalid-variable-use"><i>invalid variable
-   use</i></a> concept exists because variables can't "fail early" like other
-   syntax errors can, so by the time the user agent realizes a property value
-   is invalid, it's already thrown away the other cascaded values.
+  <p class=note>The <a href="#invalid-at-computed-value-time"><i>invalid at
+   computed-value time</i></a> concept exists because variables can't "fail
+   early" like other syntax errors can, so by the time the user agent
+   realizes a property value is invalid, it's already thrown away the other
+   cascaded values. I think &lsquo;<code class=css>attr()</code>&rsquo; needs
+   to rely on it as well, as its behavior is almost identical to variables.
 
   <h2 id=cssom><span class=secno>4. </span> APIs</h2>
 
@@ -715,15 +721,16 @@ <h2 class=no-num id=index>Index</h2>
    <li>inactive, <a href="#inactive-var-rule"
     title=inactive><strong>2.</strong></a>
 
+   <li>invalid at computed-value time, <a
+    href="#invalid-at-computed-value-time" title="invalid at computed-value
+    time"><strong>3.1.</strong></a>
+
    <li>invalid variable, <a href="#invalid-variable" title="invalid
     variable"><strong>3.1.</strong></a>
 
    <li>invalid variables, <a href="#invalid-variable" title="invalid
     variables"><strong>3.1.</strong></a>
 
-   <li>invalid variable use, <a href="#invalid-variable-use" title="invalid
-    variable use"><strong>3.1.</strong></a>
-
    <li>renderer, <a href="#renderer" title=renderer><strong>6.2.</strong></a>
 
 

css-variables/Overview.src.html

@@ -155,7 +155,7 @@ <h2 id='using-variables'>
 
 	<p>A variable can be used anywhere a value is expected in CSS.  Variables can not be used as property names, selectors, or anything else besides property values - doing so either produces an invalid value or, in some situations like the attribute value of an attribute selector, a valid value that nonetheless has no relation to the variable of that name.</p>
 
-	<p>A variable is substituted for its value in the property value at computed-value time.  If the property value, once all variables are substituted in, is invalid for the property, that is an <i>invalid variable use</i>.</p>
+	<p>A variable is substituted for its value in the property value at computed-value time.  If a declaration, once all variables are substituted in, is invalid, the declaration is <i>invalid at computed-value time</i>.</p>
 
 		<div class='example'>
 		<p>For example, the following usage is fine from a syntax standpoint, but results in nonsense when the variable is substituted in:</p>
@@ -170,9 +170,9 @@ <h2 id='using-variables'>
 <h3 id='using-invalid-variables'>
 Using Invalid Variables</h3>
 
-	<p>An <dfn title="invalid variable|invalid variables">invalid variable</dfn> results from having variables directly or indirectly refer to themselves, or from using an undefined variable.  Using an <i>invalid variable</i> results in an <i>invalid variable use</i>.</p>
+	<p>An <dfn title="invalid variable|invalid variables">invalid variable</dfn> results from having variables directly or indirectly refer to themselves, or from using an undefined variable.  Using an <i>invalid variable</i> in a property value makes the declaration <i>invalid at computed-value time</i>.</p>
 
-	<p>An <dfn>invalid variable use</dfn> results from either using an <i>invalid variable</i> in a property value, or using a valid variable that produces an invalid property value when it is substituted in.  When this happens, the property the variable is used in must compute to the property's initial value.</p>
+	<p>A declaration that is <dfn>invalid at computed-value time</dfn> results from either using an <i>invalid variable</i> in a property value, or using a valid variable that produces an invalid declaration when it is substituted in.  When this happens, the declaration must compute to the property's initial value.</p>
 
 	<div class='example'>
 		<p>For example, in the following code:</p>
@@ -182,10 +182,10 @@ <h3 id='using-invalid-variables'>
 p { background-color: red; }
 p { background-color: $invalid; }</pre>
 
-		<p>the &lt;p> elements will have transparent backgrounds (the initial value for 'background-color'), rather than red backgrounds.</p>
+		<p>the &lt;p> elements will have transparent backgrounds (the initial value for 'background-color'), rather than red backgrounds.  This is different from the second</p>
 	</div>
 
-	<p class='note'>The <i>invalid variable use</i> concept exists because variables can't "fail early" like other syntax errors can, so by the time the user agent realizes a property value is invalid, it's already thrown away the other cascaded values.</p>
+	<p class='note'>The <i>invalid at computed-value time</i> concept exists because variables can't "fail early" like other syntax errors can, so by the time the user agent realizes a property value is invalid, it's already thrown away the other cascaded values.  I think ''attr()'' needs to rely on it as well, as its behavior is almost identical to variables.</p>
 
 <h2 id='cssom'>
 APIs</h2>