[css2] Generated. Do not edit!

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

Author: bert-github

css2/colors.html

@@ -105,7 +105,11 @@ <h2><a name="q2">14.2 The background</a></h2>
 class="propinst-background-color">'background-color'</span></a>.
 </p>
 <p>
-The background of the root element becomes the background of the canvas and covers the entire <a href="intro.html#canvas">canvas</a>, anchored at the same point as it would be if it was painted only for the root element itself. The root element does not paint this background again.
+The background of the root element becomes the background of the canvas and
+covers the entire <a href="intro.html#canvas">canvas</a>, anchored (for
+<a href="colors.html#propdef-background-position" class="noxref"><span class="propinst-background-position">'background-position'</span></a>) at
+the same point as it would be if it was painted only for the root element
+itself. The root element does not paint this background again.
 </p>
 
 <p>For HTML documents, however, we recommend that authors specify the
@@ -117,7 +121,8 @@ <h2><a name="q2">14.2 The background</a></h2>
 user agents must instead use the computed value of those properties
 from that HTML element's first BODY element child when painting
 backgrounds for the canvas, and must not paint a background for that
-BODY element.
+BODY element. Such backgrounds must also be anchored at the same point
+as they would be if they were painted only for the root element.
 This does not apply to XHTML documents.
 </p>
 <div class="html-example"><p>

css2/fonts.html

@@ -545,17 +545,6 @@ <h2>15.7 <a name="font-size-props">Font size</a>: the <a href="fonts.html#propde
     <td style="width:11%">xx-large</td>
     <td style="width:8%">&nbsp;</td>
   </tr>
-  <tr>
-    <th>HTML headings</th>
-    <td>h6</td>
-    <td>&nbsp;</td>
-    <td>h5</td>
-    <td>h4</td>
-    <td>h3</td>
-    <td>h2</td>
-    <td>h1</td>
-    <td>&nbsp;</td>
-  </tr>
   <tr>
     <th>HTML font sizes</th>
     <td>1</td>

css2/syndata.html

@@ -99,7 +99,7 @@ <h3>4.1.1 <a name="tokenization">Tokenization</a></h3>
 exercising the possibilities of the latest levels of CSS.
 </p>
 <p>At the lexical level, CSS style sheets consist of a sequence of tokens.
-The list of tokens for CSS&nbsp;2.1 is as follows. The definitions use Lex-style
+The list of tokens for CSS is as follows. The definitions use Lex-style
 regular expressions. Octal codes refer to ISO 10646 (<a href="refs.html#ref-ISO10646" rel="biblioentry" class="noxref"><span class="normref">[ISO10646]</span></a>). As in
 Lex, in case of multiple matches, the longest match determines the token.
 </p>
@@ -165,6 +165,10 @@ <h3>4.1.1 <a name="tokenization">Tokenization</a></h3>
 <p>Below is the core syntax for CSS. The sections that follow describe
 how to use it. <a href="grammar.html">Appendix G</a> describes a
 more restrictive grammar that is closer to the CSS level 2 language.
+Parts of style sheets that can be parsed according to this grammar but
+not according to the grammar in Appendix G are among the parts that
+will be ignored according to the <a href="#parsing-errors>rules for
+handling parsing errors</a>.
 </p>
 <pre>
 stylesheet  : [ CDO | CDC | S | statement ]*;

css2/text.html

@@ -166,8 +166,8 @@ <h2>16.2 <a name="alignment-prop">Alignment:</a> the <a href="text.html#propdef-
 how the inline boxes within each line box align with respect to the line
 box's left and right sides; alignment is not with respect to the <a
 href="visuren.html#viewport">viewport</a>.  In the case of 'justify',
-the UA may stretch the inline boxes in addition to adjusting their
-positions. (See also <a href="text.html#propdef-letter-spacing" class="noxref"><span
+this property specifies that the inline boxes are to be made flush
+with both sides of the block. (See also <a href="text.html#propdef-letter-spacing" class="noxref"><span
 class="propinst-letter-spacing">'letter-spacing'</span></a> and <a href="text.html#propdef-word-spacing" class="noxref"><span
 class="propinst-word-spacing">'word-spacing'</span></a>.)
 </p>
@@ -619,6 +619,8 @@ <h3 id="white-space-model"><a name="q8">16.6.1 The 'white-space' processing mode
 <li>If a space (U+0020) at the end of a line has 'white-space' set to
      'normal', 'nowrap', or 'pre-line', it is also removed.
      </li>
+<li>If spaces (U+0020) or tabs (U+0009) at the end of a line have
+     'white-space' set to 'pre-wrap', UAs may visually collapse them.
 </ol>
 
 <div class="note"><p>

css2/visuren.html

@@ -851,7 +851,9 @@ <h2>9.4 <a name="normal-flow">Normal flow</a></h2>
 </p>
 <h3 id="block-formatting"><a name="q15">9.4.1 Block formatting contexts</a></h3> 
 
-<p>Floats, absolutely positioned elements, inline-blocks, table-cells, and elements with 'overflow' other than 'visible' establish new block formatting contexts.</p>
+<p>Floats, absolutely positioned elements, inline-blocks, table-cells,
+table-captions, and elements with 'overflow' other than 'visible'
+establish new block formatting contexts.</p>
 
 <p>In a block formatting context, boxes are laid out one after the
 other, vertically, beginning at the top of a containing block. The
@@ -918,8 +920,9 @@ <h3>9.4.2 <a name="inline-formatting">Inline formatting context</a></h3>
 width of the line box containing them, their horizontal distribution
 within the line box is determined by the <a href="text.html#propdef-text-align" class="noxref"><span
 class="propinst-text-align">'text-align'</span></a> property.  If that
-property has the value 'justify', the user agent may stretch the
-inline boxes as well.
+property has the value 'justify', the user agent may stretch spaces
+and words in inline boxes (except for inline-table and inline-block
+boxes) as well.
 </p>
 
 <p>
@@ -1041,9 +1044,10 @@ <h3>9.4.3 <a name="relative-positioning">Relative positioning</a></h3>
 given a position as if B1 were not offset and B2 is not re-positioned
 after B1's offset is applied. This implies that relative positioning
 may cause boxes to overlap.
-However, if relative positioning causes an 'overflow:auto' box to have
-overflow, the UA must allow the user to access this content, which,
-through the creation of scrollbars, may affect layout.
+However, if relative positioning causes an 'overflow:auto' or
+'overflow:scroll' box to have
+overflow, the UA must allow the user to access this content (at its offset
+position), which, through the creation of scrollbars, may affect layout.
 </p>
 <p>A relatively positioned box keeps its normal flow size, including
 line breaks and the space originally reserved for it. The section on
@@ -2158,7 +2162,9 @@ <h2>9.10 <a name="direction">Text direction:</a>
 not support bidirectional text may ignore the <a href="visuren.html#propdef-direction" class="noxref"><span
 class="propinst-direction">'direction'</span></a> and <a href="visuren.html#propdef-unicode-bidi" class="noxref"><span
 class="propinst-unicode-bidi">'unicode-bidi'</span></a> properties
-described in this section.
+described in this section. This exception includes UAs that render
+right-to-left characters simply because a font on the system contains them
+but do not support the concept of right-to-left text direction.
 
 <p>The characters in certain scripts are written from right to
 left. In some documents, in particular those written with the Arabic
@@ -2178,14 +2184,14 @@ <h2>9.10 <a name="direction">Text direction:</a>
 authors to specify how the elements and attributes of a document
 language map to this algorithm.
 </p>
-<p>
-If the rendered content contains right-to-left characters, and if the user
-agent displays these characters in right-to-left order, the user
-agent must apply the bidirectional algorithm. 
-(UAs that render right-to-left characters simply because a font on
-the system contains them but do not support the concept of
-right-to-left text direction are exempt from this requirement.)
-</p>
+<p>User agents that support bidirectional text must apply the Unicode
+bidirectional algorithm to every sequence of inline boxes uninterrupted
+by a forced line break or block boundary. This sequence forms the
+"paragraph" unit in the bidirectional algorithm. The paragraph embedding
+level is set according to the value of the <a href="visuren.html#propdef-direction" class="noxref"><span
+class="propinst-direction">'direction'</span></a> property of the containing
+block rather than by the heuristic given in steps P2 and P3 of the Unicode
+algorithm.</p>
 <p>Because the directionality of a text depends on the structure and
 semantics of the document language, these properties should in most
 cases be used only by designers of document type descriptions (DTDs),