[selectors4] Tweak invalid selectors section wording to add a <dfn> for Lacky

--HG--
extra : rebase_source : c7f8f8e0c5c55d1ac7cfaefbd1f18d34d1ab31ae

Author: fantasai

css3-background/Overview.src.html

@@ -2935,25 +2935,26 @@ <h3 id="the-box-shadow">Drop Shadows: the 'box-shadow' property</h3>
 the shadow shape is rounded in the same way. The 'border-image' does not
 affect the shape of the box-shadow.
 
-<p>If a spread distance is defined, the shadow is expanded outward or
-contracted inward by an operation equivalent to applying the
-absolute value of the spread value to a blur operation as defined below
+<p>If a spread distance is defined,
+the shadow is expanded outward or contracted inward by an operation equivalent to
+applying the absolute value of the spread value to a blur operation as defined below
 and thresholding the result such that for a positive spread distance all
-non-transparent pixels are given the full shadow color and for a
-negative spread distance all non-opaque pixels are made transparent.
-The UA may approximate this operation by taking an outward outset of the
-specified amount normal to the original shadow perimeter. Alternatively
-the UA may approximate the transformed shadow perimeter shape by
-outsetting (insetting, for inner shadows) the shadow's straight edges
+pixels within XXX are given the full shadow color
+and for a negative spread distance they are made transparent.
+The UA may approximate this operation by shifting each point of the shadow perimeter
+outward by the spread distance in the direction normal to the original shadow perimeter.
+Alternatively the UA may approximate the transformed shadow perimeter shape
+by outsetting (insetting, for inner shadows) the shadow's straight edges
 by the spread distance and increasing (decreasing, for inner shadows)
-and flooring at zero the corner radii by the same amount. (The UA may
-even combine these methods, using one method for outer shadows and
-another for inner ones.)
+and flooring at zero the corner radii by the same amount.
+(The UA may even combine these methods, using one method for outer shadows
+and another for inner ones.)
 For corners with a zero border-radius, however, the corner must remain
 sharp&#8212;the operation is equivalent to scaling the shadow shape.
-In any case, the effective width and height of the shadow shape is
-floored at zero. (A zero-sized shadow shape would cause an outer shadow
-to disappear, and an inner shadow to cover the entire padding-box.)
+In any case, the effective width and height of the shadowed shape
+is floored at zero.
+(A zero-sized shadowed shape would cause an outer shadow to disappear,
+and an inner shadow to cover the entire padding-box.)
 
 <p>A non-zero blur distance indicates that the resulting shadow should
 be blurred, such as by a Gaussian filter. The exact algorithm is not
@@ -3297,6 +3298,21 @@ <h3 id="exit">
 <h2 id="changes">
 Changes</h2>
 
+<h3 id="changes-2012">
+Changes since the 24 July 2012 Candidate Recommendation</h3>
+
+<p>The following (non-editorial) changes were made to this specification since the
+<a href="http://www.w3.org/TR/2012/CR-css3-background-20120724/">24 July 2012 Candidate Recommendation</a>:
+
+<ul>
+  <li>Allow <var>&lt;color></var> and ''inset'' to be interleaved in any order in 'box-shadow',
+    since they are not ambiguous and CSS generally allows variant ordering where not ambiguous.
+  <li>Allow <var>&lt;'background-clip'></var> and <var>&lt;'background-origin'></var>
+    to be separated by other component values in the 'background' shorthand,
+    since this is what is implemented.
+  <li>Clarify the definition of the spread for 'box-shadow'.
+</ul>
+
 <h3 id="changes-2012">
 Changes since the 17 April 2012 Candidate Recommendation</h3>
 

selectors4/Overview.html

@@ -9,10 +9,10 @@
    rel=dcterms.rights>
   <meta content="Selectors Level 4" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2012-11-19 name=dcterms.issued>
+  <meta content=2012-11-27 name=dcterms.issued>
   <meta content="http://dev.w3.org/csswg/selectors4/" name=dcterms.creator>
   <meta content=W3C name=dcterms.publisher>
-  <meta content="http://www.w3.org/TR/2012/ED-selectors4-20121119/"
+  <meta content="http://www.w3.org/TR/2012/ED-selectors4-20121127/"
    name=dcterms.identifier>
   <link href="../default.css" rel=stylesheet type="text/css">
   <style type="text/css">
@@ -29,14 +29,14 @@
 
    <h1 id=title>Selectors Level 4</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 19 November
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 27 November
     2012</h2>
 
    <dl>
     <dt>This version:
 
-    <dd><a href="http://www.w3.org/TR/2012/ED-selectors4-20121119/">
-     http://www.w3.org/TR/2012/ED-selectors4-20121119/</a>
+    <dd><a href="http://www.w3.org/TR/2012/ED-selectors4-20121127/">
+     http://www.w3.org/TR/2012/ED-selectors4-20121127/</a>
 
     <dt>Editor's draft:
 
@@ -1421,12 +1421,15 @@ <h3 id=namespaces><span class=secno>3.7. </span> Namespaces</h3>
   <h3 id=invalid><span class=secno>3.8. </span> Invalid Selectors and Error
    Handling</h3>
 
-  <p>Invalidity is caused by a parsing error, e.g. an unrecognized token or a
-   token which is not allowed at the current parsing point.
-
-  <p>User agents must observe the rules for handling parsing errors:
+  <p>User agents must observe the rules for handling <dfn
+   id=invalid-selectors title="invalid selector|invalid">invalid
+   selectors</dfn>:
 
   <ul>
+   <li>a parsing error in a selector, e.g. an unrecognized token or a token
+    which is not allowed at the current parsing point, causes that selector
+    to be invalid
+
    <li>a simple selector containing an <a href="#namespaces">undeclared
     namespace prefix</a> is invalid
 
@@ -1436,7 +1439,8 @@ <h3 id=invalid><span class=secno>3.8. </span> Invalid Selectors and Error
    <li>a selector list containing an invalid selector is invalid.
   </ul>
 
-  <p>An invalid selector represents nothing.
+  <p>An <a href="#invalid-selectors"><i>invalid selector</i></a> represents
+   nothing.
 
   <p class=issue>It's been <a
    href="http://lists.w3.org/Archives/Public/www-style/2010Nov/0203.html">requested</a>

selectors4/Overview.src.html

@@ -759,18 +759,18 @@ <h3 id="namespaces">
 <h3 id="invalid">
 Invalid Selectors and Error Handling</h3>
 
-  <p>Invalidity is caused by a parsing error, e.g. an unrecognized token or a token
-  which is not allowed at the current parsing point.
-
-  <p>User agents must observe the rules for handling parsing errors:
+  <p>User agents must observe the rules for handling <dfn title="invalid selector|invalid">invalid selectors</dfn>:
   <ul>
+    <li>a parsing error in a selector,
+      e.g. an unrecognized token or a token which is not allowed at the current parsing point,
+      causes that selector to be invalid
     <li>a simple selector containing an <a href="#namespaces">undeclared namespace prefix</a> is invalid
     <li>a selector containing an invalid simple selector, an invalid combinator
       or an invalid token is invalid. 
     <li>a selector list containing an invalid selector is invalid.
   </ul>
 
-  <p>An invalid selector represents nothing.
+  <p>An <i>invalid selector</i> represents nothing.
 
   <p class="issue">It's been <a href="http://lists.w3.org/Archives/Public/www-style/2010Nov/0203.html">requested</a>
     that the last rule be dropped in favor of Media Queries-style error-handling.