Remove the lingering reference to the error flag in 'consume a block'.

Author: tabatkins

css3-syntax/Overview.html

@@ -1994,10 +1994,10 @@ <h3 id=changes-from-css-2.1-tokenizer><span class=secno>3.5. </span>
    be unintentional.
 
   <p> Note that the point of this spec is to match reality; changes from
-   CSS2.1‘<code class=css>s tokenizer are nearly always because the tokeniz
-   specified something that doesn</code>’t match actual browser behavior,
-   or left something unspecified. If some detail doesn't match browsers,
-   please let me know as it's almost certainly unintentional.
+   CSS2.1‘<code class=css>s tokenizer are nearly always because the
+   tokenizer specified something that doesn</code>’t match actual browser
+   behavior, or left something unspecified. If some detail doesn't match
+   browsers, please let me know as it's almost certainly unintentional.
 
   <ol>
    <li> The DASHMATCH and INCLUDES tokens have been removed. They can instead
@@ -2012,16 +2012,18 @@ <h3 id=changes-from-css-2.1-tokenizer><span class=secno>3.5. </span>
     paying attention to opened blocks and such. Only WebKit exhibits this
     behavior, but it doesn't appear that we've gotten any compat bugs from
     it.
+
+   <li> The number, percentage, and dimension tokens have been changed to
+    include the preceding +/- sign as part of their value (rather than as a
+    separate DELIM token that needs to be manually handled every time the
+    token is mentioned in other specs). The only consequence of this is that
+    comments can no longer be inserted between the sign and the number.
+
+   <li> Several flags have been added for SVG-compatible tokenizing, so that
+    a single state machine can be used for both "vanilla" and SVG CSS
+    parsing.
   </ol>
   <!--
->  * a string ending with an EOF following backslash is now a STRING
->    instead of a BAD_STRING.
->  * BAD_STRING now contains the trailing newline character that makes
->    it a BAD_STRING.
->  * a new line following a backslash changed from a DILIM S to just a
->    DEMIM.
--->
-  <!--
 PPPPPPPPPPPPPPPPP        AAA               RRRRRRRRRRRRRRRRR      SSSSSSSSSSSSSSS EEEEEEEEEEEEEEEEEEEEEERRRRRRRRRRRRRRRRR   
 P::::::::::::::::P      A:::A              R::::::::::::::::R   SS:::::::::::::::SE::::::::::::::::::::ER::::::::::::::::R  
 P::::::PPPPPP:::::P    A:::::A             R::::::RRRRRR:::::R S:::::SSSSSS::::::SE::::::::::::::::::::ER::::::RRRRRR:::::R 
@@ -2526,8 +2528,6 @@ <h4 id=consume-a-block><span class=secno>3.6.14. </span> <dfn
    the token this algorithm was called with. (E.g. if it was called with [,
    the <a href="#ending-token"><i>ending token</i></a> is ].)
 
-  <p> The <dfn id=error-flag>error flag</dfn> is initially false.
-
   <p> Create a brace block, bracket block, or paren block as the <dfn
    id=current-block>current block</dfn>, whichever corresponds to the token
    this algorithm was called with.
@@ -2926,9 +2926,6 @@ <h2 class=no-num id=index> Index</h2>
    <li>end of the range, <a href="#end-of-the-range"
     title="end of the range"><strong>3.4.27.</strong></a>
 
-   <li>error flag, <a href="#error-flag"
-    title="error flag"><strong>3.6.14.</strong></a>
-
    <li>Hash-rest state, <a href="#hash-rest-state0"
     title="Hash-rest state"><strong>3.4.7.</strong></a>
 

css3-syntax/Overview.src.html

@@ -1978,7 +1978,7 @@ <h3>
 
 	<p>
 		Note that the point of this spec is to match reality;
-		changes from CSS2.1's tokenizer are nearly always because the tokeniz specified something that doesn't match actual browser behavior,
+		changes from CSS2.1's tokenizer are nearly always because the tokenizer specified something that doesn't match actual browser behavior,
 		or left something unspecified.
 		If some detail doesn't match browsers,
 		please let me know
@@ -2001,15 +2001,17 @@ <h3>
 			Only WebKit exhibits this behavior,
 			but it doesn't appear that we've gotten any compat bugs from it.
 
+		<li>
+			The number, percentage, and dimension tokens have been changed
+			to include the preceding +/- sign as part of their value
+			(rather than as a separate DELIM token that needs to be manually handled every time the token is mentioned in other specs).
+			The only consequence of this is that comments can no longer be inserted between the sign and the number.
+
+		<li>
+			Several flags have been added for SVG-compatible tokenizing, 
+			so that a single state machine can be used for both "vanilla" and SVG CSS parsing.
+
 	</ol>
-<!--
->  * a string ending with an EOF following backslash is now a STRING
->    instead of a BAD_STRING.
->  * BAD_STRING now contains the trailing newline character that makes
->    it a BAD_STRING.
->  * a new line following a backslash changed from a DILIM S to just a
->    DEMIM.
--->
 
 
 <!--
@@ -2517,9 +2519,6 @@ <h4>
 		The <dfn>ending token</dfn> is the mirror variant of the token this algorithm was called with.  
 		(E.g. if it was called with [, the <i>ending token</i> is ].)
 
-	<p>
-		The <dfn>error flag</dfn> is initially false.
-
 	<p>
 		Create a brace block, bracket block, or paren block as the <dfn>current block</dfn>,
 		whichever corresponds to the token this algorithm was called with.