Various fixes to errors reported by Lobotom Dysmon <http://lists.w3.org/Archives/Public/www-style/2010Nov/0098.html>

Author: fantasai

css3-page/Overview.html

@@ -695,9 +695,9 @@ <h3 id=progression><span class=secno>4.3. </span>Page Progression</h3>
     printed pages of a document would be sequenced when laid out
     side-to-side. For example, English and horizontally-set Japanese
     typically progress from left to right, whereas Arabic and vertically-set
-    Japanese pages typically progress from right to left. In documents with
-    with a left-to-right page progression the first page of the document is a
-    right page, and vice versa.</p>
+    Japanese pages typically progress from right to left. In documents with a
+    left-to-right page progression the first page of the document is a right
+    page, and vice versa.</p>
 
    <p>The page progression direction is determined as follows:</p>
 
@@ -1083,7 +1083,7 @@ <h2 id=margin-boxes><span class=secno>6. </span>Margin Boxes</h2>
      margin boxes of the binding edge of the page for the page footer.</p>
    </div>
 
-   <p>Margin boxes are oriented with respect to the content and are
+   <p>Margin boxes are positioned with respect to the page area and are
     independent of page orientation, for example the top margin boxes are
     above the page area in both portrait and landscape orientation. The
     various margin boxes are defined and illustrated in the diagram below:
@@ -1817,9 +1817,8 @@ <h2 id=page-properties><span class=secno>7. </span>Page Properties</h2>
 
      <li>The page background covers the entire page box, including the page
       margins. Background images are positioned as for any other box, by
-      default anchored within the page area (i.e. the page box's content
-      box); however if ‘<code
-      class=property>background-attachment</code>’ is ‘<code
+      default anchored within the page box's padding area; however if
+      ‘<code class=property>background-attachment</code>’ is ‘<code
       class=property>fixed</code>’ then the image is positioned relative to
       the page box including its margins.
 
@@ -2136,17 +2135,13 @@ <h3 id=page-size-prop><span class=secno>8.1. </span>Page size: the ‘<a
      indicates the size of the destination page sheet.
 
     <p>The size of a page box can either be "absolute" (fixed size) or
-     "relative" (scalable, i.e., fitting available sheet sizes).</p>
-
-    <p>The first three values in the table below can be used to create
-     relative page boxes.</p>
-
-    <p>Other values define a fixed-size page box, and thereby indicate the
-     preferred output media size. When possible, output should be rendered on
-     the media size indicated. If the specified size is not available, the
-     smallest available larger size should be used; if not available, the
-     contents of the page box should be scaled down to fit the largest
-     smaller page sheet available.</p>
+     "scalable" (i.e., fitting available sheet sizes). The first three values
+     in the table below can be used to create scalable page boxes. Other
+     values define a fixed-size page box, and thereby indicate the preferred
+     output media size. When possible, output should be rendered on the media
+     size indicated. If the specified size is not available, the rules for <a
+     href="#renderingpages">transposing a page box to a different size</a>
+     apply.</p>
 
     <p>If a <a href="#size"><code>size</code></a> property declaration is
      qualified by a ‘<code class=css>width</code>’, ‘<code
@@ -2162,6 +2157,9 @@ <h3 id=page-size-prop><span class=secno>8.1. </span>Page size: the ‘<a
      class=property>size</code></a>’: they assume the paper size that would
      be chosen if no @page rules were specified.</p>
 
+    <p class=issue>It would be useful if media queries could respond at least
+     to sizes specified on an unqualified @page.
+
     <div class=example>
      <p>In the following example
 
@@ -2359,8 +2357,7 @@ <h3 id=renderingpages><span class=secno>8.2. </span>Rendering page boxes
      that do not fit a page sheet</h3>
 
     <p>If a page box does not match the target page sheet dimensions, the
-     user agent <em class=RFC2119>MAY</em> choose (in order of preference)
-     to:</p>
+     user agent should do one of the following (in order of preference):</p>
 
     <ol>
      <li>Render the page box at the indicated size on a larger page sheet.
@@ -2443,7 +2440,7 @@ <h3 id=pg-br-before-after><span class=secno>9.1. </span>Break
       <tr>
        <th>Applies to:
 
-       <td>block-level elements
+       <td>block-level boxes, table row groups, table rows (but see prose)
 
       <tr>
        <th>Inherited:
@@ -2746,7 +2743,7 @@ <h3 id=breaks-inside><span class=secno>9.3. </span>Breaks inside
       <tr>
        <th>Applies to:
 
-       <td>block-level elements
+       <td>block containers
 
       <tr>
        <th>Inherited:
@@ -2761,7 +2758,7 @@ <h3 id=breaks-inside><span class=secno>9.3. </span>Breaks inside
       <tr>
        <th>Media:
 
-       <td>visual
+       <td>paged
 
       <tr>
        <th>Computed value:
@@ -2789,7 +2786,7 @@ <h3 id=breaks-inside><span class=secno>9.3. </span>Breaks inside
       <tr>
        <th>Applies to:
 
-       <td>block-level elements
+       <td>block containers
 
       <tr>
        <th>Inherited:
@@ -2804,7 +2801,7 @@ <h3 id=breaks-inside><span class=secno>9.3. </span>Breaks inside
       <tr>
        <th>Media:
 
-       <td>visual
+       <td>paged
 
       <tr>
        <th>Computed value:

css3-page/Overview.src.html

@@ -223,7 +223,8 @@ <h2 id="page-terms">Page Terminology</h2>
   particular printing device; but when its dimensions are known, user agents
   <em class="RFC2119">MAY</em> adjust the formatting of the document so that
   content falls within the printable area. How this adjustment is accomplished is
-  device dependent within the constraints expressed in the sections <a href="#renderingpages">Rendering page boxes that do not fit a page sheet</a> and
+  device dependent within the constraints expressed in the sections
+  <a href="#renderingpages">Rendering page boxes that do not fit a page sheet</a> and
   <a href="#content-outside-box">Content outside the page box</a>.</dd>
 
   <dt id="page-orientation">Page Orientation</dt>
@@ -422,7 +423,7 @@ <h3 id="progression">Page Progression</h3>
 is the direction in which the printed pages of a document would be sequenced
 when laid out side-to-side. For example, English and horizontally-set Japanese
 typically progress from left to right, whereas Arabic and vertically-set
-Japanese pages typically progress from right to left. In documents with with
+Japanese pages typically progress from right to left. In documents with
 a left-to-right page progression the first page of the document is a right
 page, and vice versa.</p>
 
@@ -753,7 +754,7 @@ <h2 id="margin-boxes">Margin Boxes</h2>
 could use the margin boxes of the binding edge of the page for the page footer.</p>
 </div>
 
-<p>Margin boxes are oriented with respect to the content and are independent of
+<p>Margin boxes are positioned with respect to the page area and are independent of
 page orientation, for example the top margin boxes are above the page area in
 both portrait and landscape orientation. The various margin boxes are defined
 and illustrated in the diagram below:
@@ -1273,7 +1274,7 @@ <h2 id="page-properties">Page Properties</h2>
   and <a href="#margin-box-dimensions">Computing Margin Box Dimensions</a>.
   <li>The page background covers the entire page box, including the page margins.
   Background images are positioned as for any other box, by default anchored
-  within the page area (i.e. the page box's content box); however if
+  within the page box's padding area; however if
   'background-attachment' is 'fixed' then the image is positioned relative to
   the page box including its margins.</li>
   <li>The rules for counter scoping are modified <a href="page-based-counters">as
@@ -1510,17 +1511,16 @@ <h3 id="page-size-prop">Page size: the 'size' property</h3>
 In the general case, where one page box is rendered onto one <a href="#page-sheet">page sheet</a>,
 the 'size' property also indicates the size of the destination page sheet.
 
-<p>The size of a page box can either be "absolute" (fixed size) or "relative"
-(scalable, i.e., fitting available sheet sizes).</p>
-
-<p>The first three values in the table below can be used to create relative page
-boxes.</p>
-
-<p>Other values define a fixed-size page box, and thereby indicate the preferred
+<p>The size of a page box can either be "absolute" (fixed size) or "scalable"
+(i.e., fitting available sheet sizes).
+The first three values in the table below can be used to create scalable page
+boxes.
+Other values define a fixed-size page box, and thereby indicate the preferred
 output media size. When possible, output should be rendered on the media size
-indicated. If the specified size is not available, the smallest available
-larger size should be used; if not available, the contents of the page box
-should be scaled down to fit the largest smaller page sheet available.</p>
+indicated.
+If the specified size is not available, the rules for
+<a href="#renderingpages">transposing a page box to a different size</a>
+apply.</p>
 
 <p>If a <code>size</code> property declaration is qualified by a ''width'',
 ''height'', ''device-width'', ''device-height'', ''aspect-ratio'',
@@ -1531,6 +1531,9 @@ <h3 id="page-size-prop">Page size: the 'size' property</h3>
 queries do not honor 'size': they assume the paper size that would be chosen
 if no @page rules were specified.</p>
 
+<p class=issue>It would be useful if media queries could respond at least
+to sizes specified on an unqualified @page.
+
 <div class="example">
   <p>In the following example
   <pre>
@@ -1695,7 +1698,7 @@ <h4 id="page-size-media-query">Media Queries</h4>
 <h3 id="renderingpages">Rendering page boxes that do not fit a page sheet</h3>
 
 <p>If a page box does not match the target page sheet dimensions, the user agent
-<em class="RFC2119">MAY</em> choose (in order of preference) to:</p>
+should do one of the following (in order of preference):</p>
 
 <ol>
   <li>Render the page box at the indicated size on a larger page sheet.</li>
@@ -1753,7 +1756,7 @@ <h3 id="pg-br-before-after">Break before/after elements: <span class="property">
     <td>auto
   <tr>
     <th>Applies to:
-    <td>block-level elements
+    <td>block-level boxes, table row groups, table rows (but see prose)
   <tr>
     <th>Inherited:
     <td>no
@@ -1964,7 +1967,7 @@ <h3 id="breaks-inside">Breaks inside elements: 'orphans', 'widows'</h3>
     <td>2
   <tr>
     <th>Applies to:
-    <td>block-level elements
+    <td>block containers
   <tr>
     <th>Inherited:
     <td>yes
@@ -1973,7 +1976,7 @@ <h3 id="breaks-inside">Breaks inside elements: 'orphans', 'widows'</h3>
     <td>N/A
   <tr>
     <th>Media:
-    <td>visual
+    <td>paged
   <tr>
     <th>Computed value:
     <td>specified value
@@ -1991,7 +1994,7 @@ <h3 id="breaks-inside">Breaks inside elements: 'orphans', 'widows'</h3>
     <td>2
   <tr>
     <th>Applies to:
-    <td>block-level elements
+    <td>block containers
   <tr>
     <th>Inherited:
     <td>yes
@@ -2000,7 +2003,7 @@ <h3 id="breaks-inside">Breaks inside elements: 'orphans', 'widows'</h3>
     <td>N/A
   <tr>
     <th>Media:
-    <td>visual
+    <td>paged
   <tr>
     <th>Computed value:
     <td>specified value