[CSS22] Updated for errata s.4.1.1e, about parsing at-rules in declaration lists.

Author: bert-github

css2/changes.src

@@ -264,7 +264,7 @@ changes and most changes to examples are not listed here.</p>
     <blockquote>
      <p>Boxes in the normal flow belong to a <span class="index-def"
      title="formatting context">formatting context</span>, which
-     <ins>in CSS&nbsp;2.2</ins> may be <ins>table,</ins> block or
+     <ins>in CSS&nbsp;2</ins> may be <ins>table,</ins> block or
      inline<del>, but not both simultaneously</del>. <ins>In future
      levels of CSS, other types of formatting context will be
      introduced.</ins> <a href="#block-level">Block-level</a> boxes
@@ -766,7 +766,7 @@ term
 
      <p><del>Except for table boxes, which are described in a later
       chapter, and replaced elements,</del> <ins>In
-      CSS&nbsp;2.2,</ins> a block-level box is also a block container
+      CSS&nbsp;2,</ins> a block-level box is also a block container
       box <ins>unless it is a table box or the principal box of a
       replaced element</ins>. A <dfn >block container box</dfn> either
       contains only block-level boxes or establishes an inline
@@ -898,7 +898,7 @@ term
 
      <p><ins>However, if no boxes are generated for the element whose
       background would be used for the background of the canvas, then
-      the canvas background is transparent. (in CSS&nbsp;2.2, that is the
+      the canvas background is transparent. (in CSS&nbsp;2, that is the
       case when the element or an ancestor has 'display: none'.)</ins>
 
      <p><ins>Note that, if the element has 'visibility: hidden' but
@@ -934,6 +934,105 @@ term
     <!-- Status: not edited, waiting for concrete text -->
     <!-- https://lists.w3.org/Archives/Public/www-style/2015Jul/0032.html -->
 
+
+
+   <li id=s.4.1.1e class=change>
+    <p><span class=updated>[2015-09-05]</span> Malformed declarations
+     are handled differently when the start of the malformed
+     declaration conforms to the syntax of an at-rule. In that case,
+     parsing resumes not at the next semicolon or at the closing curly
+     brace of the enclosing block, but immediately after that
+     at-rule. This is expressed by adding the at-rule to the core
+     syntax for rulesets, as shown below.
+
+    <p>In <a href="syndata.html#tokenization" >&ldquo;4.1.1
+     Tokenization&rdquo;,</a> change the production for ruleset as
+     follows:
+
+    <blockquote>
+     <pre>
+<del>ruleset     : selector? '{' S* declaration? [ ';' S* declaration? ]* '}' S*;</del>
+<ins>ruleset     : selector? '{' S* declaration-list '}' S*;
+declaration-list: declaration [ ';' S* declaration-list ]?
+              | at-rule declaration-list
+              | /* empty */;</ins></pre>
+    </blockquote>
+
+    <p>In <a href="syndata.html#rule-sets" >&ldquo;4.1.7 Rule sets,
+     declaration blocks, and selectors&rdquo;,</a> change the second
+     paragraph as follows:
+
+    <blockquote>
+     <p>A declaration block starts with a left curly brace ({) and
+      ends with the matching right curly brace (}). In between there
+      must be a list of zero or more <del>semicolon-separated (;)
+      declarations</del> <ins>declarations and at-rules. Declarations
+      must end with a semicolon (;) unless they are last in the
+      list.</ins>
+
+     <p class=note><ins>Note: CSS level&nbsp;2 has no at-rules that
+      may appear inside rule sets, but such at-rules may be defined in
+      future levels.</ins>
+    </blockquote>
+
+    <p>In <a href="syndata.html#parsing-errors" >&ldquo;4.2 Rules for
+     handling parsing errors&rdquo;,</a> change the rule for malformed
+     declarations as follows:
+
+    <blockquote>
+     <ul>
+      <li>
+       <p><strong>Malformed declarations.</strong> User agents must
+	handle unexpected tokens encountered while parsing a
+	declaration by reading until the end of the declaration, while
+	observing the rules for matching pairs of (), [], {}, "", and
+	'', and correctly handling escapes. For example, a malformed
+	declaration may be missing a property name, colon (:), or
+	property value.
+
+       <p><ins>When the UA expects the start of a declaration or
+	at-rule (i.e., an IDENT token or an ATKEYWORD token) but finds
+	an unexpected token instead, that token is considered to be
+	the first token of a malformed declaration. I.e., the rule for
+	malformed declarations, rather than malformed statements is
+	used to determine which tokens to ignore in that case.</ins>
+
+       <p>The following are all equivalent:
+
+       <pre class=example>
+<code>p { color:green }
+<ins>p { @foo { bar: baz } color:green }  /* unknown at-rule */</ins>
+p { color:green; color }  /* malformed declaration missing ':', value */
+p { color:red;   color; color:green }  /* same with expected recovery */
+p { color:green; color: } /* malformed declaration missing value */
+p { color:red;   color:; color:green } /* same with expected recovery */
+p { color:green; color{;color:maroon} } /* unexpected tokens { } */
+	 p { color:red;   color{;color:maroon}; color:green } /* same with recovery */</code></pre>
+       </li>
+     </ul>
+    </blockquote>
+
+    <p>And, finally, in <a href="page.html#page-box" >&ldquo;13.2 Page
+     boxes: the @page rule&rdquo,</a> remove the following text, which
+     is now redundant:
+
+    <blockquote>
+     <p><del>The rules for handling malformed declarations, malformed
+      statements, and invalid at-rules inside @page are as defined in
+      <a href="syndata.html#parsing-errors" >section&nbsp;4.2,</a>
+      with the following addition: when the UA expects the start of a
+      declaration or at-rule (i.e., an IDENT token or an ATKEYWORD
+      token) but finds an unexpected token instead, that token is
+      considered to be the first token of a malformed
+      declaration. I.e., the rule for malformed declarations, rather
+      than malformed statements is used to determine which tokens to
+      ignore in that case.</del>
+    </blockquote>
+
+    <!-- Status: edited -->
+    <!-- http://lists.w3.org/Archives/Public/www-style/2013May/0783.html -->
+
+
   </ul>
 
 </BODY>