[css2] Issues 69, 84, 111, 127, 128, 131, 136, and 141 from

bert-github · bert-github · commit a398e1c57bdf · 2010-04-19T16:12:37.000Z
http://wiki.csswg.org/spec/css2.1 --HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402972
diff --git a/css2/changes.src b/css2/changes.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: changes.src,v 2.114 2009-08-31 17:39:31 bbos Exp $ -->
+<!-- $Id: changes.src,v 2.115 2010-04-19 16:12:36 bbos Exp $ -->
 <HEAD>
 <TITLE>Changes</TITLE>
 </HEAD>
@@ -4051,7 +4051,7 @@ status of a draft.
 
 <!--========================== issue 123 =========================-->
 
-<h3 id="s.4.2"><a
+<h3 id="s.4.2b"><a
 href="/TR/2009/CR-CSS2-20090423/syndata.html#parsing-errors">
 Section&nbsp;4.2 Rules for handling parsing errors</a></h3>
 
@@ -4070,7 +4070,7 @@ first.
 
 <!--========================== issue 89 ==========================-->
 
-<h3 id="s.13.3.3"><a
+<h3 id="s.13.3.3c"><a
 href="/TR/2009/CR-CSS2-20090423/page.html#allowed-page-breaks">
 Section&nbsp;13.3.3 Allowed page breaks</a></h3>
 
@@ -4157,7 +4157,7 @@ class="propinst-height">'height'</span> on row groups.</ins>
 
 <!--========================== issue 124 =========================-->
 
-<h3 id="s.G"><a
+<h3 id="s.Ga"><a
 href="/TR/2009/CR-CSS2-20090423/grammar.html">
 Appendix&nbsp;G. Grammar of CSS 2.1</a></h3>
 
@@ -4166,6 +4166,180 @@ grammar. (The ambiguities only affected spaces and were harmless.)
 
 <!--===============================================================-->
 
+<h2><a name=errata3>Errata since the Candidate Recommendation of
+September 2009</a></h2>
+
+<p>These are the errata for <a
+href="http://www.w3.org/TR/2009/CR-CSS2-20090908">CSS level&nbsp;2
+revision&nbsp;1, CR version of 8&nbsp;September 2009.</a> These
+corrections have the status of a draft.
+
+<!--========================== issue 128 ==========================-->
+
+<h3 id="t.3.1"><a
+href="/TR/2009/CR-CSS2-20090908/conform.html#defs">
+Section&nbsp;3.1 Definitions</a></h3>
+
+<p><span class=date>[2010-04-19]</span> Add a clarification to the
+definition of replaced element:
+
+<blockquote>
+<p>The content of replaced elements is not considered in the CSS
+rendering model.
+</blockquote>
+
+<p>(Previously, the definition only said that the content was
+&ldquo;outside the scope of CSS.&rdquo;)
+
+<!--========================== issue 136 ==========================-->
+
+<h3 id="t.4.1.2.2"><a
+href="/TR/2009/CR-CSS2-20090908/syndata.html#vendor-keyword-history">
+Section&nbsp;4.1.2.2 Informative Historical Notes</a></h3>
+
+<p><span class=date>[2010-04-19]</span> Add &ldquo;-tc-&rdquo; to the
+list of existing vendor prefixes.
+
+<!--========================== issue 141 ==========================-->
+
+<h3 id="t.9.2.3"><a
+href="/TR/2009/CR-CSS2-20090908/syndata.html#length-units">
+Section&nbsp;4.3.2 Lengths</a></h3>
+
+<p><span class=date>[2010-04-19]</span> Make explicit that 'ex', when
+used in the 'font-size' property, refers to the <em>parent
+element's</em> 'ex' (just as 'em' refers to the parent's 'em' in that
+case.)
+
+<!--========================== issue 128 ==========================-->
+
+<h3 id="t.9.2.3a"><a
+href="/TR/2009/CR-CSS2-20090908/visuren.html#run-in">
+Section&nbsp;9.2.3 Run-in boxes</a></h3>
+
+<p><span class=date>[2010-04-19]</span> Make the definition of
+'run-in' more precise:
+
+<blockquote>
+<p><del>A <dfn>run-in box</dfn> behaves as follows:</del>
+
+<ol>
+<li><del>If the run-in box contains a block box, the run-in box
+becomes a block box.</del>
+
+<li><del>If a sibling block box (that does not float and is not
+absolutely positioned) follows the run-in box, the run-in box becomes
+the first inline box of the block box.  A run-in cannot run in to a
+block that already starts with a run-in or that itself is a
+run-in.</del>
+
+<li><del>Otherwise, the run-in box becomes a block box.</del>
+</ol>
+
+<p><ins>A <dfn>run-in element</dfn> (or pseudo-element) <var>A</var>
+behaves as follows:</ins>
+  
+<ol>
+  <li><ins>If <var>A</var> has any children that inhibit run-in
+  behavior (see below), then <var>A</var> is rendered as if it had
+  'display: block'.</ins>
+
+  <li><ins>Let <var>B</var> be the first of <var>A</var>'s following
+  siblings that is neither floating nor absolutely positioned nor has
+  'display: none'. If <var>B</var> exists and has a specified value
+  for 'display' of 'block' or 'list-item' and is not replaced, then
+  <var>A</var> is rendered as an 'inline' element at the start of
+  <var>B</var>'s principal box. Note: <var>A</var> is rendered before
+  <var>B</var>'s ':before' pseudo-element, if any. See 12.1.</ins>
+
+  <li><ins>Otherwise, <var>A</var> is rendered as if it had 'display:
+  block'.</ins>
+</ol>
+
+<p><ins>In the above, "siblings" and "children" include both normal
+elements and :before/:after pseudo-elements.</ins>
+
+<p><ins>An element or pseudo-element <var>C</var> <dfn>inhibits run-in
+behavior</dfn> if one of the following is true. (Note that the
+definition is recursive.)</ins>
+
+<ol>
+  <li><ins><var>C</var> is not floating and not absolutely positioned
+  and the computed value of its 'display' is one of 'block',
+  'list-item', 'table' or 'run-in'.</ins>
+
+  <li><ins><var>C</var> has a computed value for 'display' of 'inline'
+  and it has one or more children that inhibit run-in behavior. (Where
+  "children" includes both normal elements and :before/:after
+  pseudo-elements.)</ins>
+</ol>
+</blockquote>
+
+<p>It remains undefined how 'run-in' and ':first-line' interact:
+
+<blockquote>
+<p><ins>It is undefined in CSS&nbsp;2.1 if a run-in inherits from a
+':first-line' pseudo-element.</ins>
+</blockquote>
+
+<!--========================== issue 69 ===========================-->
+
+<h3 id="t.9.6.1"><a
+href="/TR/2009/CR-CSS2-20090908/visuren.html#fixed-positioning">
+Section&nbsp;9.6.1 Fixed positioning</a></h3>
+
+<p><span class=date>[2010-04-19]</span> 'Fixed' backgrounds in paged
+media are positioned relative to the page box (and thus repeat on
+every page, just like 'fixed' elements). The position of fixed
+backgrounds in paged media was previously undefined.
+
+<!--========================== issue 111 ==========================-->
+
+<h3 id="t.15.6"><a
+href="/TR/2009/CR-CSS2-20090908/fonts.html#font-boldness">
+Section&nbsp;15.6 Font boldness: the 'font-weight' property</a></h3>
+
+<p><span class=date>[2010-04-19]</span> The meaning of the keywords
+'bolder' and 'lighter' no longer depends on both the inherited weight
+and the actually used font, but only on the inherited weight.
+
+<!--========================== issue 84 ===========================-->
+
+<h3 id="t.16.4"><a
+href="/TR/2009/CR-CSS2-20090908/text.html#spacing-props">
+Section&nbsp;16.4 Letter and word spacing: the 'letter-spacing' and
+'word-spacing' properties</a></h3>
+
+<p><span class=date>[2010-04-19]</span> Word spacing does not affect
+fixed-width spaces. Change:
+
+<blockquote>
+<p>Word spacing affects each space (U+0020)<del>,</del><ins> and</ins>
+non-breaking space (U+00A0) <del>and ideographic space (U+3000)</del>,
+left in the text after the white space processing rules have been
+applied. <ins>The effect of the property on other word-separator
+characters is undefined. However general punctuation, characters with
+zero advance width (such as the zero with space U+200B) and
+fixed-width spaces (such as U+3000 and U+2000 through U+200A) are not
+affected.</ins>
+</blockquote>
+
+<!--========================== issue 127 ==========================-->
+
+<h3 id="t.17.4"><a
+href="/TR/2009/CR-CSS2-20090908/tables.html#model">
+Section&nbsp;17.4 Tables in the visual formatting model</a></h3>
+
+<p><span class=date>[2010-04-19]</span> The caption of the image still
+describes the image as it was in the previous version. Change:
+
+<blockquote>
+<p>Diagram of a table with a caption above it<del>; the top margin of
+the caption is collapsed with the top margin of the table</del>.
+</blockquote
+
+<!--===============================================================-->
+
 </BODY>
 </HTML>
 
diff --git a/css2/conform.src b/css2/conform.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: conform.src,v 2.86 2009-05-13 12:59:58 bbos Exp $ -->
+<!-- $Id: conform.src,v 2.87 2010-04-19 16:12:36 bbos Exp $ -->
 <HEAD>
 <TITLE>Conformance: requirements and recommendations</TITLE>
 
@@ -141,6 +141,9 @@ document changed intrinsic size depending on the user's bank balance,
 then the UA might want to act as if that resource had no intrinsic
 dimensions.
 
+<p>The content of replaced elements is not considered in the CSS
+rendering model.
+
 <dt><strong><span class="index-def" title="intrinsic
 dimensions"><a name="intrinsic">Intrinsic dimensions</a></span></strong>
 
diff --git a/css2/fonts.src b/css2/fonts.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: fonts.src,v 2.97 2009-08-31 17:39:31 bbos Exp $ -->
+<!-- $Id: fonts.src,v 2.98 2010-04-19 16:12:36 bbos Exp $ -->
 <head>
 <title>Fonts</title>
 <meta name="editor" lang="tr" content="Tantek &Ccedil;elik">
@@ -512,24 +512,34 @@ value to "Ice Prawn ExtraBlack".</p>
 </table>
 </div>
 
+<p>Values of 'bolder' and 'lighter' indicate values relative to the
+weight of the parent element.  Based on the inherited weight value,
+the weight used is calculated using the chart below.  Child elements
+inherit the calculated weight, not a value of 'bolder' or 'lighter'.
 
-<p>Since the intent of the relative keywords 'bolder' and 'lighter' is
-to darken or lighten the face <em>within the family</em> and because a
-family may not have faces aligned with all the symbolic weight values,
-the matching of 'bolder' is to the next darker face available on the
-client within the family and the matching of 'lighter' is to the next
-lighter face within the family. To be precise, the meaning of the
-relative keywords 'bolder' and 'lighter' is as follows:
-</p>
-<ul>
-<li>'bolder' selects the next weight that is assigned to a font that
-is darker than the inherited one.
-</li>
-<li>'lighter' is similar, but works in the opposite direction: it
-selects the next lighter keyword with a different font from the
-inherited one.
-</li>
-</ul>
+<table summary="The keywords bolder and lighter stand for a specific
+weight as a function of the inherited weight, as defined by this
+table.">
+<caption>The meaning of 'bolder' and 'lighter'</caption>
+<thead>
+<tr><th>Inherited value   <th>bolder  <th>lighter
+<tbody>
+<tr><td>100               <td>400     <td>100
+<tr><td>200               <td>400     <td>100
+<tr><td>300               <td>400     <td>100
+<tr><td>400               <td>700     <td>100
+<tr><td>500               <td>700     <td>100
+<tr><td>600               <td>900     <td>400
+<tr><td>700               <td>900     <td>400
+<tr><td>800               <td>900     <td>700
+<tr><td>900               <td>900     <td>700
+</table>
+
+<p>The table above is equivalent to selecting the next relative bolder
+or lighter face, given a font family containing normal and bold faces
+along with a thin and a heavy face. Authors who desire finer control
+over the exact weight values used for a given element should use
+numerical values instead of relative weights.
 
 <p>There is no guarantee that there will be a darker face for each of
 the 'font-weight' values; for example, some fonts may have only a
diff --git a/css2/syndata.src b/css2/syndata.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: syndata.src,v 2.172 2009-08-31 17:33:46 bbos Exp $ -->
+<!-- $Id: syndata.src,v 2.173 2010-04-19 16:12:36 bbos Exp $ -->
 <head>
 <title>Syntax and basic data types</title>
 <meta name="editor" lang="tr" content="Tantek &Ccedil;elik">
@@ -229,6 +229,7 @@ href="#parsing-errors">rules for handling parsing errors</a>. However, because t
 <tr><td><code>-hp-</code></td><td>Hewlett Packard</td></tr>
 <tr><td><code>-ro-</code></td><td>Real Objects</td></tr>
 <tr><td><code>-rim-</code></td><td>Research In Motion</td></tr>
+<tr><td><code>-tc-</code></td><td>Tall Components</td></tr>
 </tbody>
 </table>
 
@@ -860,7 +861,12 @@ quad-width in typographic texts.)
 </p>
 <p>The <span class="index-def" title="x-height|ex (unit)"><a
 name="ex">'ex'</a></span> unit is defined by the element's first available
-font. The <span class="descinst-x-height">'x-height'</span> is so called
+font.
+The exception is when 'ex' occurs in the value of the <span
+class="propinst-font-size">'font-size'</span> property, in which case
+it refers to the 'ex' of the parent element.
+
+<p>The <span class="descinst-x-height">'x-height'</span> is so called
 because it is often equal to the height of the lowercase "x". However,
 an 'ex' is defined even for fonts that do not contain an "x".</p>
 <p>The x-height of a font can be found in different ways. Some fonts
diff --git a/css2/tables.src b/css2/tables.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: tables.src,v 2.117 2010-01-26 23:48:48 fantasai Exp $ -->
+<!-- $Id: tables.src,v 2.118 2010-04-19 16:12:36 bbos Exp $ -->
 <head>
 <title>Tables</title>
 </head>
@@ -476,9 +476,7 @@ values for those properties.
 <p><img src="images/table_container.png" alt="A table with a caption above
 it">
 
-<p class="caption">Diagram of a table with a caption above it; the
-top margin of the caption is collapsed with the top margin of the
-table.
+<p class="caption">Diagram of a table with a caption above it.
 </div>
 
 <h3><a name="caption-position">Caption position and alignment</a></h3>
diff --git a/css2/text.src b/css2/text.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: text.src,v 2.70 2009-08-06 21:05:30 dbaron Exp $ -->
+<!-- $Id: text.src,v 2.71 2010-04-19 16:12:37 bbos Exp $ -->
 <head>
 <title>Text</title>
 <meta http-equiv="Content-Style-Type" content="text/css">
@@ -323,9 +323,13 @@ implementation-specific limits. </dd>
 <p>Word spacing algorithms are user agent-dependent.  Word spacing is
 also influenced by justification (see the <span
 class="propinst-text-align">'text-align'</span> property).
-Word spacing affects each space (U+0020), non-breaking space (U+00A0),
-and ideographic space (U+3000) left in the text after the white space
-processing rules have been applied.</p>
+Word spacing affects each space (U+0020) and non-breaking space
+(U+00A0), left in the text after the white space processing rules have
+been applied. The effect of the property on other word-separator
+characters is undefined. However general punctuation, characters with
+zero advance width (such as the zero with space U+200B) and
+fixed-width spaces (such as U+3000 and U+2000 through U+200A) are not
+affected.
 
 <div class="example"><p>
 In this example, the word-spacing between each word in H1 elements is
diff --git a/css2/visuren.src b/css2/visuren.src
