[css2] Updates

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

Author: ianbjacobs

css2/errata.src

@@ -25,7 +25,7 @@ hspace="0"></a><br clear="all"></p>
 <dd><a href="_THE_UPDATE_DIR_/_THE_ID_-errata.html">
 _THE_UPDATE_DIR_/_THE_ID_-errata.html</a>
 <dt>Last revised: 
-<dd>$Date: 1999-06-29 22:17:52 $
+<dd>$Date: 1999-11-02 18:31:44 $
 </dl>
 
 <dl>
@@ -56,7 +56,11 @@ do not enforce this rule: 'border-top', 'border-right',
 <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".
+<UL>
+<LI>The "nmchar" token should also allow the range "A-Z".
+<LI>In the rule for "any" (in the core syntax), change "FUNCTION"
+to "FUNCTION any* ')'".
+</UL>
 
 <H3><a href="syndata.html#values">Section 4.3 (Double sign problem)</a></H3>
 
@@ -84,6 +88,16 @@ initial sign only:</P>
 <LI><a href="syndata.html#angle-units">Angles</a>
 </UL>
 
+<H3><a href="syndata.html#color-units">Section 4.3.6</a></H3>
+
+<P>Delete the comments about range
+restriction after the following examples:
+
+<PRE>
+EM { color: rgb(255,0,0) }      
+EM { color: rgb(100%, 0%, 0%) } 
+</PRE>
+
 <H3><a href="visuren.html#choose-position">Section 9.3.1</a></H3>
 
 <P>The definition of the value 'static' should
@@ -173,6 +187,12 @@ explanation for the variable "a" is missing and should read:</P>
 <P>'Totum' and 'Kodic' is not a 'serif' but 'sans-serif'. 'pathang' is
 not a 'sans-serif' but 'serif'.
 
+<h3><a href="tables.html#q2"> 17.2</a></h3>
+
+<P>In the definition of <strong>table-header-group</strong>, change
+"footer" to "header" in "Print user agents may repeat footer rows on
+each page spanned by a table."
+
 <h2><a name="minor-errors">Minor Typographical Errors</a></h2>
 
 <h3><a href="intro.html#q1">Section 2.1</a></h3>
@@ -195,7 +215,7 @@ 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>
+<h3><a href="selector.html#lang">Section 5.11.4</a></h3>
 
 <P>In "XML uses an attribute called XML:LANG", the
 XML attribute should be in lowercase, i.e., xml:lang.
@@ -227,8 +247,13 @@ user and author rules...".
 
 <h3><a href="box.html#border-color-properties">Section 8.5.2</a></h3>
 
-<P>The individual border-X-color property definitions may
+<UL>
+<LI>
+The individual border-X-color property definitions may
 also take the value 'transparent'.
+<LI>The 'border-color' shorthand property should read:
+<PRE>[ &lt;color&gt; | transparent ]{1,4} | inherit</PRE>
+</UL>
 
 <h3><a href="visuren.html#q5">Section 9.2.1</a></h3>
 
@@ -245,13 +270,57 @@ anonymous initial boxes is inherited from the P, but the background is transpare
 
 <P>In the second paragraph, "a new a new" should only read "a new".
 
+<h3><a href="visudet.html#q15">Section 10.6.1</a></h3>
+
+<P>The <span class="propinst-height">'height'</span> property doesn't
+apply. The height of the content area is equal to the actual font size
+of the element. The vertical padding, border and margin of an inline,
+non-replaced box start at the top and bottom of the font, not the
+<span class="propinst-line-height">'line-height'</span>. But only the
+<span class="propinst-line-height">'line-height'</span> is used to
+compute the height of the line box.
+
+<P>If more than one font size is used (this could happen when glyphs
+are found in different fonts), the height of the content area is not
+defined by this specification. However, we recommend that the largest
+font size determine the content height.
+
 <h3><a href="generate.html#content">Section 12.2</a></h3>
 
 <P>In the definition of &lt;counter&gt;, the sentence "The latter
 function also has two forms: 'counter(name, string)' or 'counter(name,
 string, style)'" should read "two forms: 'counters(name, string)' or
 'counters(name, string, style)'"
 
+<h3><a href="generate.html#markers">Section 12.6.1</a></h3>
+
+<P>Change the third paragraph as follows:
+
+<BLOCKQUOTE>
+<P>For the :before pseudo-element, the baseline in the marker box will
+be vertically aligned with the baseline in the first line box of the
+principal box. If the principal box contains no line boxes, or if
+there is a block box within the principal box that is above the first
+line box, the top outer edge of the marker box will be aligned with
+the top outer edge of the principal box. 
+
+<P>For the :after pseudo-element, the baseline in the marker box will
+be vertically aligned with the baseline in the last line box in the
+principal box.  If the principal box contains no line boxes, or if
+there is a block box within the principal box that is below the last
+line box, the bottom outer edge of the marker box will be aligned with
+the bottom outer edge of the principal box.
+</BLOCKQUOTE>
+
+<h3><a href="page.html#page-box">Section 13.2</a></h3>
+
+<P>In the following code, put a ":" after "size".
+
+<PRE>
+@page { size 8.5in 11in; margin: 2cm }
+</PRE>
+
+
 <h3><a href="colors.html#gamma-correction">Section 14.3</a></h3>
 
 <P>The first sentence has one too many "the"s in
@@ -270,6 +339,17 @@ whitespace characters inside the font name is converted to a single space.
 
 <P>all occurrences of the word "font" should be replaced by "voice family".
 
+<h3><a href="grammar.html#q2">Section D.2 Lexical scanner </a></h3>
+
+<P>Remove "RGB S*" from the rule "term" since rgb() is covered by
+the "function" production, which matches counter(), atrr(), format(),
+and others as well.
+
+<h3><a href="grammar.html#tokenizer-diffs">Section D.3 Comparison of tokenization in CSS2 and CSS1 </a></h3>
+
+<P>In the last bullet, change <code>.\55ft</code> to 
+<code>.\35 5ft</code>. 
+
 <h3><a href="sample.html">Sample Style Sheet for HTML 4.0</a></h3>
 
 <P>The value of the 'line-height' property set for the BODY
@@ -293,6 +373,36 @@ whitespace in this case.
 inherited. This applies even to properties for which values
 do not otherwise inherit.
 
+<h3><a href="box.html#box-dimensions">Section 8.1</a></h3>
+
+<UL>
+<LI>From the definition of "padding edge", delete the sentence "The
+padding edge of a box defines the edges of the containing block
+established by the box." For information about containing
+blocks, consult <a href="visudet.html#containing-block-details">
+Section 10.1</a>.
+
+<LI>Border backgrounds are not specified by border properties. Change
+the last paragraph of 8.1 to:
+<BLOCKQUOTE>
+<P>The background style of the content, padding, and border areas of a
+box is specified by the <span
+class="propinst-background">'background'</span> property of the
+generating element. Margin backgrounds are always transparent.
+</BLOCKQUOTE>
+</UL>
+
+<h3><a href="box.html#collapsing-margins">Section 8.3.1</a></h3>
+
+<P>Add this clarifying note to the first bullet of the explanation
+of vertical collapsing of margins:</P>
+
+<BLOCKQUOTE>
+<P><strong>Note.</strong> Adjoining boxes may be generated by
+elements that are not related as siblings or ancestors.
+</BLOCKQUOTE>
+
+
 <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
@@ -302,9 +412,20 @@ where one or more splits occur.
 
 <h3><a href="visuren.html#relative-positioning">Section 9.4.3</a></h3>
 
+<P>Relatively positioned boxes do not always establish new containing
+blocks. Change the second paragraph to:</P>
+
+<BLOCKQUOTE>
+<p>A relatively positioned box keeps its normal flow size, including
+line breaks and the space originally reserved for it. The section on
+<a href="#containing-block">containing blocks</a> explains when a
+relatively positioned box establishes a new containing block.
+</BLOCKQUOTE>
+
 <P>The following attempts to clarify the meaning of the 'left',
-'right', 'top' and 'bottom' properties for relative positioning.
+'right', 'top' and 'bottom' properties for relative positioning:
 
+<BLOCKQUOTE>
 <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
@@ -348,13 +469,95 @@ 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').
+</BLOCKQUOTE>
+
+<h3><a href="visuren.html#direction">Section 9.10</a></h3>
+
+<P>In this sentence of the last paragraph:</p>
+
+<BLOCKQUOTE>
+<P>Conforming HTML user agents may therefore ignore the 'direction'
+and 'unicode-bidi' properties in author and user style sheets.
+</BLOCKQUOTE>
+
+<P>the word "ignore" means that if a 'unicode-bidi' or 'direction'
+value conflicts with the HTML 4.0 "dir" attribute value, then user
+agents may choose to use the "dir" value rather than the CSS
+properties.
+
+<P>User agents are not required to support the <span
+class="propinst-direction">'direction'</span> and <span
+class="propinst-unicode-bidi">'unicode-bidi'</span> properties to
+conform to CSS2 unless they support bi-directional text rendering
+(except for the case of HTML 4.0 as noted above).
+
+<h3><a href="visudet.html#propdef-line-height">Section 10.8.1</a></h3>
+
+<P>Clarify this paragraph:
+
+<BLOCKQUOTE>
+<P>Note that replaced elements have a 'font-size' and a 'line-height'
+property, even if they are not used directly to determine the height
+of the box. The 'font-size' is, however, used to define the 'em' and
+'ex' units, and the 'line-height' has a role in the 'vertical-align'
+property.
+</BLOCKQUOTE>
+
+<P>as follows:
+
+<BLOCKQUOTE>
+<P>Note that replaced elements have a <span
+class="propinst-font-size">'font-size'</span> and a <span
+class="propinst-line-height">'line-height'</span> property, even if
+they are not used directly to determine the height of the box: 'em'
+and 'ex' values are relative to values of <span
+class="propinst-font-size">'font-size'</span> and percentage values
+for <span class="propinst-vertical-align">'vertical-align'</span> are
+relative to values of <span
+class="propinst-line-height">'line-height'</span>.
+</BLOCKQUOTE>
+
+<h3><a href="visufx.html#clipping">Section 11.1.2</a></h3>
+
+<P>Values of "rect()" should be separated by commas. Thus, the
+definition of &lt;shape&gt; should start:</p>
+
+<BLOCKQUOTE>
+<P>In CSS2, the only valid &lt;shape&gt; value is: rect (&lt;top&gt;, &lt;right&gt;, &lt;bottom&gt;,
+&lt;left&gt;) ...
+</BLOCKQUOTE>
+
+<P>Due to this ambiguity, user agents may support separation of
+offsets in "rect()" with or without commas.
+
+<h3><a href="ui.html#system-colors">Section 18.2</a></h3>
+
+
+<P>For the 'ButtonHighlight' value, change the description
+from "Dark shadow" to "Highlight color".
+
 
 <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="changes">Changes</a></h2>
+
+<P>The following changes are proposed by the CSS Working Group.
+Please note that these changes have "working draft" status and
+may not be considered definitive unless incorporated into
+a revised Recommendation. 
+
+<h3><a href="visufx.html#clipping">Section 11.1.2</a></h3>
+
+<P>While CSS2 specifies that values of "rect()" specify offsets from
+the respective sides of the box, current implementations interpret
+values with respect to the top and left edges for <em>all</em>
+four values (top, right, bottom, and left). The Working Group
+proposes to revise CSS2 to conform to current practice.
+
 <!-- <h2><a name="open-issues">Open Issues</a></h2> -->
 </BODY>
 </HTML>