[css2] Removed initial date

--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%401745

Author: ianbjacobs

css2/errata.src

@@ -19,14 +19,13 @@ src="http://www.w3.org/Icons/w3c_home.gif" alt="W3C" align="left" border="0"
 hspace="0"></a><br clear="all"></p>
 
 <H1 align="center">Errata in _THE_ID_</H1>
-<p align="center">12-May-1998</p>
 
 <dl>
 <dt>This document:
 <dd><a href="_THE_UPDATE_DIR_/_THE_ID_-errata.html">
 _THE_UPDATE_DIR_/_THE_ID_-errata.html</a>
 <dt>Last revised: 
-<dd>$Date: 1998-09-28 23:23:23 $
+<dd>$Date: 1999-01-08 16:35:33 $
 </dl>
 
 <dl>
@@ -54,6 +53,11 @@ do not enforce this rule: 'border-top', 'border-right',
 'border-bottom', 'border-left', 'border', 'background', 'font',
 'list-style', 'cue', and 'outline'.
 
+<H3><a href="syndata.html#tokenization">Section 4.1.1</a> (and
+<a href="grammar.html#q2">D2</a>)</H3>
+
+<P>The "nmchar" token should also allow the range "A-Z".
+
 <H3><a href="syndata.html#values">Section 4.3 (Double sign problem)</a></H3>
 
 <P>Several values described in subsections of this section
@@ -134,6 +138,26 @@ relatively positioned boxes are considered without their offset). Note
 that the child box may be an <a
 href="visuren.html#anonymous-block-level">anonymous box.</a>
 
+<h3><a href="visufx.html#overflow">Section 11.1.1</a></h3>
+
+<P>The example of a DIV element containing a BLOCKQUOTE
+containing another DIV is not rendered correctly. The first
+rule:
+
+<PRE>
+DIV { width : 100px; height: 100px;
+      border: thin solid red;
+      }
+</PRE>
+
+<P>Applies to both the external and internal DIV, so, for
+example, the internal DIV box should be rendered
+with a red border. The intention of the authors was 
+that the first style rule only apply to the external DIV.
+This could be accomplished by making it more specific by
+adding a "class" or "id" value to the markup and changing
+the selectors accordingly.
+
 <h3><a href="fonts.html#font-size-props">Section 15.2.4</a></h3>
 
 <P>Under the 'font-size-adjust' property, in the formula given
@@ -171,6 +195,11 @@ tree."
 <P>The correct RFC number for the registration of the
 "text/css" content type is RFC 2318, not RFC 2138.
 
+<h3><a href="selector.html#lang">Section 5.11.1</a></h3>
+
+<P>In "XML uses an attribute called XML:LANG", the
+XML attribute should be in lowercase, i.e., xml:lang.
+
 <h3><a href="selector.html#first-line-pseudo">Section 5.12.1</a></h3>
 
 <P>The rendering of the first example is:</P>
@@ -209,7 +238,12 @@ should end instead with the end tag "&lt;/P&gt;".
 
 <h3><a href="visuren.html#anonymous">Section 9.2.2, Anonymous inline boxes</a></h3>
 
-<P>In the (third paragraph) sentence "In the example, the color of the anonymous initial boxes is inherited from the P, but the background is transparent", substitute the word "inline" for "initial". 
+<P>In the (third paragraph) sentence "In the example, the color of the
+anonymous initial boxes is inherited from the P, but the background is transparent", substitute the word "inline" for "initial". 
+
+<h3><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
+
+<P>In the second paragraph, "a new a new" should only read "a new".
 
 <h3><a href="generate.html#content">Section 12.2</a></h3>
 
@@ -245,13 +279,81 @@ element should be "1.12em".
 
 <h2><a name="clarifications">Clarifications</a></h2>
 
+<h3><a href="selector.html#descendant-selectors">Section 5.5</a></h3>
+
+<P>Near the end of the section, the text 'Note the whitespace on
+either side of the "*"' may be misleading. The note is not meant to
+imply that whitespace is required on both sides of the "*" (since the
+grammar does not require it in this case) but that one may use
+whitespace in this case.
+
+<h3><a href="cascade.html#value-def-inherit">Section 6.2.1</a></h3>
+
+<P>The 'inherit' value causes the properties value to be
+inherited. This applies even to properties for which values
+do not otherwise inherit.
+
 <h3><a href="visuren.html#inline-formatting">Section 9.4.2</a></h3>
 
 <P>The statement "When an inline box is split, margins, borders, and
 padding have no visual effect where the split occurs." may be
 generalized. Margins, borders, and padding have no visual effect
 where one or more splits occur.
 
+<h3><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
+
+<P>The following attempts to clarify the meaning of the 'left',
+'right', 'top' and 'bottom' properties for relative positioning.
+
+<P>For relatively positioned elements, 'left' and 'right' move the
+box(es) horizontally, without changing their size. 'Left' moves the
+boxes to the right, and 'right' moves them to the left. Since boxes
+are not split or stretched as a result of 'left' or 'right', the
+computed values are always: left = -right.
+
+<P>If both 'left' and 'right' are 'auto' (their initial values), the
+computed values are '0' (i.e., the boxes stay in their original
+position).
+
+<P>If 'left' is 'auto', its computed value is minus the value of 'right'
+(i.e., the boxes move to the left by the value of 'right').
+
+<P>If 'right' is specified as 'auto', its computed value is minus the
+value of 'left'.
+
+<P>If neither 'left' nor 'right' is 'auto', the position is
+over-constrained, and one of them has to be ignored. If the
+'direction' property is 'ltr', the value of 'left' wins and 'right'
+becomes -'left'. If 'direction' is 'rtl', 'right' wins and 'left' is
+ignored.
+
+<div class="example">
+<P><strong>Example.</strong> 
+The following two style sheets are equivalent:
+
+<PRE>
+    DIV.a8 { position: relative; left: -1em; right: auto }
+</PRE>
+
+and
+
+<PRE>
+    DIV.a8 { position: relative; left: auto; right: 1em }
+</PRE>
+</div>
+
+<P>The 'top' and 'bottom' properties move relatively positioned
+elements up or down.  They also must be each other's negative. If both
+are 'auto', their computed values are both '0'. If one of them is
+'auto', it becomes the negative of the other. If neither is 'auto',
+'bottom' is ignored (i.e., the computed value of 'bottom' will be
+minus the value of 'top').
+
+<h3><a href="aural.html#speaking-props">Section 19.3</a></h3>
+
+<P>The parenthetical phrase "somewhat analogous to the 'display' property"
+is misleading. The 'speak' property resembles 'visibility' in
+some ways and 'display' in others.
 
 <h2><a name="open-issues">Open Issues</a></h2>