[dbaron revision history] Merge in the rest of the CSS 2.1 syndata.html changes. (date: 2003/08/07 21:24:14)

Author: dbaron

css3-syntax/Overview.src.html

@@ -173,8 +173,8 @@ <h2>CSS style sheet representation</h2>
 using one of the first two methods.</p>
 
 <p>At most one @charset rule may appear in an external
-style sheet -- it must <em>not</em> appear in an embedded style sheet
--- and it must appear at the very start of the style sheet, not preceded
+style sheet &mdash; it must <em>not</em> appear in an embedded style sheet
+&mdash; and it must appear at the very start of the style sheet, not preceded
 by any characters (except for the optional Byte Order Mark <a
 href="#BOM">described
 above)</a>. After "@charset", authors specify the name of a
@@ -366,8 +366,8 @@ <h3 id="tokenization">Tokenization</h3>
 <p class="issue">[This needs to be integrated with the selectors module.
 How should that be done?]</p>
 
-<p>All levels of CSS -- level 1, level 2, level 3, and any future levels
--- use the same core syntax. This allows UAs to parse (though not
+<p>All levels of CSS &mdash; level 1, level 2, level 3, and any future levels
+&mdash; use the same core syntax. This allows UAs to parse (though not
 completely understand) style sheets written in levels of CSS that didn't
 exist at the time the UAs were created. Designers can use this feature
 to create style sheets that work with older user agents, while also
@@ -901,9 +901,10 @@ <h2 id="error-handling">Rules for handling parsing errors or unsupported feature
 more of the other rules as well.</p>
 
 <p class="issue">[A general comment on how to handle negative numbers
-when disallowed might be useful.  It should probably be a parsing error.
-We might want to add additional grammar productions for potentially
-negative numbers.]</p>
+when disallowed might be useful.  It should be a parsing error (and thus
+ignored).  We might want to add additional grammar productions for
+potentially negative numbers.]</p>
+
 </li>
 
 <li><strong>Malformed declarations.</strong>  User agents must handle
@@ -953,6 +954,33 @@ <h2 id="error-handling">Rules for handling parsing errors or unsupported feature
 <PRE class="example">
 h1 { color: blue }
 </PRE>
+<li>
+
+<li id="unsupportedvalues">
+
+<p><strong>Unsupported Values</strong>If a UA does not support a
+particular value, it should <em>ignore</em> that value when parsing
+stylesheets, as if that value was an <a href="#illegalvalues">illegal
+value</a>.  For example:</p>
+
+<div class="example">
+<pre>
+  h3 {
+    display: inline;
+    display: run-in;
+  }
+</pre>
+</div>
+
+<p>  
+A UA that supports the 'run-in' value for the 'display' property will
+accept the first display declaration and then "write over" that value with
+the second display declaration. A UA that does not support the 'run-in'
+value will process the first display declaration and ignore the second
+display declaration.
+</p>
+
+</li>
 
 </UL>