Address various editorial nits.

Author: fantasai

css3-values/Overview.html

@@ -28,13 +28,13 @@
 
    <h1>CSS Values and Units Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 16 July 2012</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 17 July 2012</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://www.w3.org/TR/2012/ED-css3-values-20120716/">http://www.w3.org/TR/2012/ED-css3-values-20120716/</a>
+     href="http://www.w3.org/TR/2012/ED-css3-values-20120717/">http://www.w3.org/TR/2012/ED-css3-values-20120717/</a>
 
     <dt>Latest version:
 
@@ -394,14 +394,21 @@ <h3 id=component-types><span class=secno>2.1. </span> Component value types</h3>
   <p>Some property value definitions also include the slash (/) and/or the
    comma (,) as literals. These represent their corresponding tokens.
 
-  <p>All CSS properties also accept the keyword values ‘<a
-   href="#inherit"><code class=css>inherit</code></a>’ and ‘<a
-   href="#initial"><code class=css>initial</code></a>’ as their property
-   value, but for readability these are not listed explicitly in the property
-   value syntax definitions. These keywords cannot be combined with other
-   component values in same declaration; such a declaration is invalid. For
-   example, ‘<code class=css>background: url(corner.png) no-repeat,
-   inherit;</code>’ is invalid.
+  <p>All CSS properties also accept the <a href="#common-keywords">CSS-wide
+   keyword values</a> ‘<a href="#inherit"><code
+   class=css>inherit</code></a>’ and ‘<a href="#initial"><code
+   class=css>initial</code></a>’ as the sole component of their property
+   value. For readability these are not listed explicitly in the property
+   value syntax definitions. For example, the full value definition of <a
+   href="http://www.w3.org/TR/css3-background/#border-color">‘<code
+   class=property>border-color</code>’</a> is ‘<code class=css>[
+   &lt;color>{1,4} ] | inherit | initial</code>’ (even though it is listed
+   as ‘<code class=css>&lt;color>{1,4}</code>’).
+
+  <p class=note> Note: This implies that, in general, combining these
+   keywords with other component values in the same declaration results in an
+   invalid declaration. For example, ‘<code class=css>background:
+   url(corner.png) no-repeat, inherit;</code>’ is invalid.
 
   <h3 id=component-combinators><span class=secno>2.2. </span> Component value
    combinators</h3>
@@ -431,6 +438,10 @@ <h3 id=component-combinators><span class=secno>2.2. </span> Component value
   <pre>
 <!---->  a b   |   c ||   d &&   e f
 <!---->[ a b ] | [ c || [ d && [ e f ]]]</pre>
+  <!--
+	<p>
+		White space is allowed, but optional, between components of a combination.
+-->
 
   <h3 id=component-multipliers><span class=secno>2.3. </span> Component value
    multipliers</h3>
@@ -455,6 +466,11 @@ <h3 id=component-multipliers><span class=secno>2.3. </span> Component value
    <li>A hash mark (#) indicates that the preceding type, word, or group
     occurs one or more times, separated by comma tokens.
   </ul>
+  <!--
+	<p>
+		White space is allowed, but optional, between repetitions
+		and around the comma separator of ''#''-multiplied lists.
+-->
 
   <p>For repeated component values (indicated by ‘<code
    class=css>*</code>’, ‘<code class=css>+</code>’, or ‘<code
@@ -465,12 +481,12 @@ <h3 id=component-multipliers><span class=secno>2.3. </span> Component value
   <h3 id=component-whitespace><span class=secno>2.4. </span> Component values
    and white space</h3>
 
-  <p>Component values are specified in terms of tokens, as described in <a
-   href="http://www.w3.org/TR/CSS21/syndata.html#tokenization">Chapter 4</a>
-   of <a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. As the
-   grammar allows spaces between tokens in the components of the
-   <code>value</code> production, spaces may appear between components in
-   property values.
+  <p>Unless otherwise specified, white space and/or comments may appear
+   before, after, and/or between components in a property value or
+   subcomponents in a <a href="#functional-notation">functional notation</a>
+   that is defined using these component <a
+   href="#component-combinators">combinators</a> and <a
+   href="#component-multipliers">multipliers</a>.
 
   <p class=note>Note: In many cases, spaces will in fact be <em>required</em>
    between components in order to distinguish them from each other. For
@@ -614,7 +630,7 @@ <h4 id=common-keywords><span class=secno>3.1.1. </span> CSS-wide keywords:
    initial value. <a href="#CSS3CASCADE"
    rel=biblioentry>[CSS3CASCADE]<!--{{CSS3CASCADE}}--></a>
 
-  <p class=note> The <dfn id=default>‘<code
+  <p class=note> Note, the <dfn id=default>‘<code
    class=css>default</code>’</dfn> keyword is reserved for future use.
 
   <h3 id=strings><span class=secno>3.2. </span> Quoted Strings: the ‘<a
@@ -701,10 +717,10 @@ <h3 id=urls><span class=secno>3.3. </span> Resource Locators: the ‘<a
   <p>In order to create modular style sheets that are not dependent on the
    absolute location of a resource, authors should use relative URIs.
    Relative URIs (as defined in <a href="#URI"
-   rel=biblioentry>[URI]<!--{{URI}}--></a>) are resolved to full URIs using a
-   base URI. RFC 3986, section 3, defines the normative algorithm for this
-   process. For CSS style sheets, the base URI is that of the style sheet,
-   not that of the source document.
+   rel=biblioentry>[URI]<!--{{!URI}}--></a>) are resolved to full URIs using
+   a base URI. RFC 3986, section 3, defines the normative algorithm for
+   this process. For CSS style sheets, the base URI is that of the style
+   sheet, not that of the source document.
 
   <p>When a <a href="#url-value"><i>&lt;url></i></a> appears in the computed
    value of a property, it is resolved to an absolute URL, as described in
@@ -755,23 +771,23 @@ <h3 id=integers><span class=secno>4.1. </span> Integers: the ‘<a
    corresponds to a subset of the <a href="#number"><code>NUMBER</code></a>
    token in the <a
    href="http://www.w3.org/TR/CSS21/syndata.html#tokenization">grammar</a>.
-   Integers may be immediately preceded by ‘<code class=css>-</code>’ or
-   ‘<code class=css>+</code>’ to indicate the sign.
+   The first digit of an integer may be immediately preceded by ‘<code
+   class=css>-</code>’ or ‘<code class=css>+</code>’ to indicate the
+   integer's sign.
 
   <h3 id=numbers><span class=secno>4.2. </span> Numbers: the ‘<a
    href="#number-value"><code class=css>&lt;number></code></a>’ type</h3>
 
   <p>Number values are denoted by <dfn
    id=number-value><var>&lt;number></var></dfn>. A <dfn
-   id=number>number</dfn> is either an <a
-   href="#integer-value"><var>&lt;integer></var></a>, or zero or more decimal
+   id=number>number</dfn> is either an &lt;integer> or zero or more decimal
    digits followed by a dot (.) followed by one or more decimal digits. It
    corresponds to the <a href="#number"><code>NUMBER</code></a> token in the
    <a
    href="http://www.w3.org/TR/CSS21/syndata.html#tokenization">grammar</a>.
-   Like integers, numbers may also be immediately preceded by ‘<code
-   class=css>-</code>’ or ‘<code class=css>+</code>’ to indicate the
-   sign.
+   As with integers, the first character of a number may be immediately
+   preceded by ‘<code class=css>-</code>’ or ‘<code
+   class=css>+</code>’ to indicate the number's sign.
 
   <h3 id=percentages><span class=secno>4.3. </span> Percentages: the ‘<a
    href="#percentage-value"><code class=css>&lt;percentage></code></a>’
@@ -1304,13 +1320,15 @@ <h3 id=position><span class=secno>7.3. </span> 2D Positioning: the ‘<a
   <h2 id=functional-notation><span class=secno>8. </span> Functional
    Notations</h2>
 
-  <p>Some values use a <dfn id=functional-notation0>functional notation</dfn>
-   to type values and to lump values together. The syntax starts with the
-   name of the function immediately followed by a left parenthesis followed
-   by the argument(s) to the notation followed by a right parenthesis. If a
-   function takes a list of arguments, the arguments are separated by a comma
-   (‘<code class=css>,</code>’) with optional whitespace before and after
-   the comma.
+  <p> A <dfn id=functional-notation0>functional notation</dfn> is a type of
+   component value that can represent more complex types or invoke special
+   processing. The syntax starts with the name of the function immediately
+   followed by a left parenthesis (i.e. a <code>FUNCTION</code> token)
+   followed by the argument(s) to the notation followed by a right
+   parenthesis. White space is allowed, but optional, immediately inside the
+   parentheses. If a function takes a list of arguments, the arguments are
+   separated by a comma (‘<code class=css>,</code>’) with optional
+   whitespace before and after the comma.
 
   <pre class=example>
 <!-- -->background: url(http://www.example.org/image);
@@ -1685,8 +1703,8 @@ <h3 id=attr-notation><span class=secno>8.3. </span> Attribute References:
    href="http://dev.w3.org/csswg/css3-namespace/#css-qnames">CSS qualified
    name</a> (the wqname production in <a href="#CSS3NAMESPACE"
    rel=biblioentry>[CSS3NAMESPACE]<!--{{!CSS3NAMESPACE}}--></a>) that
-   represents an attribute name. <span class=note>Most of the time, this will
-   just be an identifier.</span>
+   represents an attribute name. (In the absence of namespacing, this will
+   just be a CSS identifier.)
 
   <p> The optional <var>&lt;type-or-unit></var> argument is a keyword drawn
    from the list below that tells the UA how to interpret the attribute
@@ -1699,6 +1717,12 @@ <h3 id=attr-notation><span class=secno>8.3. </span> Attribute References:
    property. If it's absent, the default value for the given
    <var>&lt;type-or-unit></var> (from the list below) is implied.
 
+  <p class=note> Note that, unlike ‘<a href="#toggle"><code
+   class=css>toggle()</code></a>’ <var>&lt;value></var>s, an ‘<a
+   href="#attr"><code class=css>attr()</code></a>’ <var>&lt;fallback></var>
+   value may contain top-level commas, as it is always the last argument in
+   the functional notation.
+
   <p> The attr() expression is only valid if:
 
   <ul>
@@ -1887,17 +1911,17 @@ <h3 id=attr-notation><span class=secno>8.3. </span> Attribute References:
 }
 metal {
 	background: silver url(metal.png);
-}
-
+}</pre>
+  </div>
+  <!--
 /* this also uses a possible extension to the 'content' property
 to handle replaced content and alternatives to unavailable,
 corrupted or unsupported content */
 img {
 	content: replaced attr(src url), attr(alt string, none);
 	height: attr(height px, auto);
 	width: attr(width px, auto);
-}</pre>
-  </div>
+}-->
 
   <div class="illegal example">
    <p>All of the following examples are invalid and would cause a parse-time
@@ -2304,6 +2328,16 @@ <h3 class=no-num id=normative-references>Normative references</h3>
     href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
     </dd>
    <!---->
+
+   <dt id=URI>[URI]
+
+   <dd>T. Berners-Lee; R. Fielding; L. Masinter. <a
+    href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource
+    Identifiers (URI): generic syntax.</cite></a> January 2005. Internet RFC
+    3986. URL: <a
+    href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
+    </dd>
+   <!---->
   </dl>
   <!--end-normative-->
 
@@ -2333,16 +2367,6 @@ <h3 class=no-num id=other-references>Other references</h3>
     href="http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/">http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/</a>
     </dd>
    <!---->
-
-   <dt id=URI>[URI]
-
-   <dd>T. Berners-Lee; R. Fielding; L. Masinter. <a
-    href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource
-    Identifiers (URI): generic syntax.</cite></a> January 2005. Internet RFC
-    3986. URL: <a
-    href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
-    </dd>
-   <!---->
   </dl>
   <!--end-informative-->