W3C home > Mailing lists > Public > public-css-commits@w3.org > January 2012

csswg/css3-break Overview.html,1.6,1.7 Overview.src.html,1.7,1.8

From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 24 Jan 2012 21:51:48 +0000
To: public-css-commits@w3.org
Message-Id: <E1RpoHM-0006DM-0d@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-break
In directory hutz:/tmp/cvs-serv23874

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Shift 'page' section so that generic break controls are all together

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- Overview.html	24 Jan 2012 19:51:13 -0000	1.6
+++ Overview.html	24 Jan 2012 21:51:45 -0000	1.7
@@ -139,50 +139,62 @@
      <li><a href="#values"><span class=secno>1.2. </span> Values</a>
     </ul>
 
-   <li><a href="#page-breaks"><span class=secno>2. </span> Page Breaks</a>
+   <li><a href="#fragmentation-model"><span class=secno>2. </span>
+    Fragmentation Model and Terminology</a>
     <ul class=toc>
-     <li><a href="#pg-br-before-after"><span class=secno>2.1. </span>
+     <li><a href="#page-breaks"><span class=secno>2.1. </span> Page
+      Breaks</a>
+    </ul>
+
+   <li><a href="#breaking-controls"><span class=secno>3. </span> Breaking
+    Controls</a>
+    <ul class=toc>
+     <li><a href="#pg-br-before-after"><span class=secno>3.1. </span>
       Breaking before/after/inside elements: the &lsquo;<code
       class=property>page-break-before</code>&rsquo;, &lsquo;<code
       class=property>page-break-after</code>&rsquo;, and &lsquo;<code
       class=property>page-break-inside</code>&rsquo; properties </a>
 
-     <li><a href="#using-named-pages"><span class=secno>2.2. </span> Using
-      named pages: the &lsquo;<code class=property>page</code>&rsquo;
-      property</a>
-
-     <li><a href="#breaks-inside"><span class=secno>2.3. </span> Breaks
+     <li><a href="#breaks-inside"><span class=secno>3.2. </span> Breaks
       inside elements: &lsquo;<code class=property>orphans</code>&rsquo;,
       &lsquo;<code class=property>widows</code>&rsquo;</a>
 
-     <li><a href="#allowed-pg-brk"><span class=secno>2.4. </span> Allowed
+     <li><a href="#using-named-pages"><span class=secno>3.3. </span> Using
+      named pages: the &lsquo;<code class=property>page</code>&rsquo;
+      property</a>
+    </ul>
+
+   <li><a href="#breaking-rules"><span class=secno>4. </span> Rules for
+    Breaking</a>
+    <ul class=toc>
+     <li><a href="#allowed-pg-brk"><span class=secno>4.1. </span> Allowed
       page breaks</a>
 
-     <li><a href="#forced-pg-brk"><span class=secno>2.5. </span> Forced page
+     <li><a href="#forced-pg-brk"><span class=secno>4.2. </span> Forced page
       breaks</a>
 
-     <li><a href="#best-pg-brk"><span class=secno>2.6. </span> "Best" page
+     <li><a href="#best-pg-brk"><span class=secno>4.3. </span> "Best" page
       breaks</a>
     </ul>
 
-   <li><a href="#conformance"><span class=secno>3. </span> Conformance</a>
+   <li><a href="#conformance"><span class=secno>5. </span> Conformance</a>
     <ul class=toc>
-     <li><a href="#conventions"><span class=secno>3.1. </span> Document
+     <li><a href="#conventions"><span class=secno>5.1. </span> Document
       Conventions</a>
 
-     <li><a href="#conformance-classes"><span class=secno>3.2.
+     <li><a href="#conformance-classes"><span class=secno>5.2.
       </span>Conformance Classes</a>
 
-     <li><a href="#partial"><span class=secno>3.3. </span> Partial
+     <li><a href="#partial"><span class=secno>5.3. </span> Partial
       Implementations</a>
 
-     <li><a href="#experimental"><span class=secno>3.4. </span> Experimental
+     <li><a href="#experimental"><span class=secno>5.4. </span> Experimental
       Implementations</a>
 
-     <li><a href="#testing"><span class=secno>3.5. </span> Non-Experimental
+     <li><a href="#testing"><span class=secno>5.5. </span> Non-Experimental
       Implementations</a>
 
-     <li><a href="#cr-exit-criteria"><span class=secno>3.6. </span> CR Exit
+     <li><a href="#cr-exit-criteria"><span class=secno>5.6. </span> CR Exit
       Criteria</a>
     </ul>
 
@@ -251,7 +263,10 @@
    inherit</a> keyword as their property value. For readability it has not
    been repeated explicitly.
 
-  <h2 id=page-breaks><span class=secno>2. </span> Page Breaks</h2>
+  <h2 id=fragmentation-model><span class=secno>2. </span> Fragmentation Model
+   and Terminology</h2>
+
+  <h3 id=page-breaks><span class=secno>2.1. </span> Page Breaks</h3>
 
   <p> The following sections explain page breaking in CSS3 paged media. Five
    properties indicate where the user agent may or should break pages, and on
@@ -266,7 +281,9 @@
    the page, through an ensuing blank page if one exists, and onto the top of
    the subsequent page.
 
-  <h3 id=pg-br-before-after><span class=secno>2.1. </span> Breaking
+  <h2 id=breaking-controls><span class=secno>3. </span> Breaking Controls</h2>
+
+  <h3 id=pg-br-before-after><span class=secno>3.1. </span> Breaking
    before/after/inside elements: the &lsquo;<a
    href="#page-break-before"><code
    class=property>page-break-before</code></a>&rsquo;, &lsquo;<a
@@ -456,26 +473,26 @@
    is in the normal flow of the root element. User agents may also apply
    these properties to other boxes.
 
-  <h3 id=using-named-pages><span class=secno>2.2. </span> Using named pages:
-   the &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
-   property</h3>
+  <h3 id=breaks-inside><span class=secno>3.2. </span> Breaks inside elements:
+   &lsquo;<a href="#orphans"><code class=property>orphans</code></a>&rsquo;,
+   &lsquo;<a href="#widows"><code class=property>widows</code></a>&rsquo;</h3>
 
   <table class=propdef summary="property definition">
    <tbody>
     <tr>
      <th>Name:
 
-     <td><dfn id=page>page</dfn>
+     <td><dfn id=orphans>orphans</dfn>
 
     <tr>
      <th>Value:
 
-     <td>auto | &lt;identifier&gt;
+     <td>&lt;integer&gt;
 
     <tr>
      <th>Initial:
 
-     <td>auto
+     <td>2
 
     <tr>
      <th>Applies to:
@@ -485,7 +502,7 @@
     <tr>
      <th>Inherited:
 
-     <td>no (but see prose)
+     <td>yes
 
     <tr>
      <th>Percentages:
@@ -495,7 +512,7 @@
     <tr>
      <th>Media:
 
-     <td>paged
+     <td>visual
 
     <tr>
      <th>Computed value:
@@ -503,84 +520,12 @@
      <td>specified value
   </table>
 
-  <p> The &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
-   property is used to specify a particular type of page where an element
-   should be displayed.
-
-  <div class=example>
-   <p>This example will put all tables on a right-hand side landscape page
-    (named "rotated"):</p>
-
-   <pre>
-@page rotated { size: landscape }
-table { page: rotated; page-break-before: right }
-      </pre>
-  </div>
-
-  <p> The &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
-   property works as follows: If a block box with inline content has a
-   &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
-   property that is different from the preceding block box with inline
-   content, then one or two page breaks are inserted between them, and the
-   boxes after the break are rendered on a page box of the named type. See <a
-   href="#forced-pg-brk">"Forced page breaks" below</a>.
-
-  <p> The &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
-   property does not inherit. However, if the &lsquo;<a href="#page"><code
-   class=property>page</code></a>&rsquo; value on an element is &lsquo;<code
-   class=css>auto</code>&rsquo;, then it is treated as having the same name
-   as its nearest ancestor with a non-auto value. When indicated on the root
-   element, the effective name is the empty string.
-
-  <p> Because a previous version of this specification indicated that the
-   &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
-   property is inherited, an implementation that inherits the &lsquo;<a
-   href="#page"><code class=property>page</code></a>&rsquo; property and
-   treats &lsquo;<code class=css>auto</code>&rsquo; as always naming the
-   empty string remains conformant to CSS3 Paged Media. Therefore authors
-   should not explicitly specify the &lsquo;<code
-   class=css>auto</code>&rsquo; value on a descendant of an element with a
-   non-&lsquo;<code class=css>auto</code>&rsquo; &lsquo;<a href="#page"><code
-   class=property>page</code></a>&rsquo; value as the resulting behavior will
-   be unpredictable.
-
-  <p> Page names are case-sensitive identifiers. However the &lsquo;<code
-   class=css>auto</code>&rsquo; value, being a CSS keyword, is <a
-   href="http://www.w3.org/TR/CSS21/syndata.html#characters">case-insensitive</a>.
-   
-
-  <div class=example>
-   <p> In this example, the two tables are rendered on landscape pages
-    (indeed, on the same page, if they fit). The page type "narrow" is used
-    for the &lt;p&gt; after the second table, as the page properties for the
-    table element are no longer in effect:</p>
-
-   <pre>
-@page narrow { size: 9cm 18cm }
-@page rotated { size: landscape }
-div { page: narrow }
-table { page: rotated }</pre>
-
-   <p> with this document:</p>
-
-   <pre>
-&lt;div&gt;
-&lt;table&gt;...&lt;/table&gt;
-&lt;table&gt;...&lt;/table&gt;
-&lt;p&gt;This text is rendered on a 'narrow' page&lt;/p&gt;
-&lt;/div&gt;</pre>
-  </div>
-
-  <h3 id=breaks-inside><span class=secno>2.3. </span> Breaks inside elements:
-   &lsquo;<a href="#orphans"><code class=property>orphans</code></a>&rsquo;,
-   &lsquo;<a href="#widows"><code class=property>widows</code></a>&rsquo;</h3>
-
   <table class=propdef summary="property definition">
    <tbody>
     <tr>
      <th>Name:
 
-     <td><dfn id=orphans>orphans</dfn>
+     <td><dfn id=widows>widows</dfn>
 
     <tr>
      <th>Value:
@@ -618,22 +563,46 @@
      <td>specified value
   </table>
 
+  <p> The &lsquo;<a href="#orphans"><code
+   class=property>orphans</code></a>&rsquo; property specifies the minimum
+   number of line boxes in a block element that must be left at the bottom of
+   a page. The &lsquo;<a href="#widows"><code
+   class=property>widows</code></a>&rsquo; property specifies the minimum
+   number of line boxes of a block element that must be left at the top of a
+   page. Examples of how they are used to control page breaks are given
+   below.
+
+  <p> Only positive integers are allowed as values of &lsquo;<a
+   href="#orphans"><code class=property>orphans</code></a>&rsquo; and
+   &lsquo;<a href="#widows"><code class=property>widows</code></a>&rsquo;.
+   Negative values and zero are invalid must cause the declaration to be <a
+   href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.
+
+  <p> If a block contains fewer lines than the value of &lsquo;<a
+   href="#widows"><code class=property>widows</code></a>&rsquo; or &lsquo;<a
+   href="#orphans"><code class=property>orphans</code></a>&rsquo;, the rule
+   simply becomes that all lines in the block must be kept together.
+
+  <h3 id=using-named-pages><span class=secno>3.3. </span> Using named pages:
+   the &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
+   property</h3>
+
   <table class=propdef summary="property definition">
    <tbody>
     <tr>
      <th>Name:
 
-     <td><dfn id=widows>widows</dfn>
+     <td><dfn id=page>page</dfn>
 
     <tr>
      <th>Value:
 
-     <td>&lt;integer&gt;
+     <td>auto | &lt;identifier&gt;
 
     <tr>
      <th>Initial:
 
-     <td>2
+     <td>auto
 
     <tr>
      <th>Applies to:
@@ -643,7 +612,7 @@
     <tr>
      <th>Inherited:
 
-     <td>yes
+     <td>no (but see prose)
 
     <tr>
      <th>Percentages:
@@ -653,7 +622,7 @@
     <tr>
      <th>Media:
 
-     <td>visual
+     <td>paged
 
     <tr>
      <th>Computed value:
@@ -661,27 +630,76 @@
      <td>specified value
   </table>
 
-  <p> The &lsquo;<a href="#orphans"><code
-   class=property>orphans</code></a>&rsquo; property specifies the minimum
-   number of line boxes in a block element that must be left at the bottom of
-   a page. The &lsquo;<a href="#widows"><code
-   class=property>widows</code></a>&rsquo; property specifies the minimum
-   number of line boxes of a block element that must be left at the top of a
-   page. Examples of how they are used to control page breaks are given
-   below.
+  <p> The &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
+   property is used to specify a particular type of page where an element
+   should be displayed.
 
-  <p> Only positive integers are allowed as values of &lsquo;<a
-   href="#orphans"><code class=property>orphans</code></a>&rsquo; and
-   &lsquo;<a href="#widows"><code class=property>widows</code></a>&rsquo;.
-   Negative values and zero are invalid must cause the declaration to be <a
-   href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.
+  <div class=example>
+   <p>This example will put all tables on a right-hand side landscape page
+    (named "rotated"):</p>
 
-  <p> If a block contains fewer lines than the value of &lsquo;<a
-   href="#widows"><code class=property>widows</code></a>&rsquo; or &lsquo;<a
-   href="#orphans"><code class=property>orphans</code></a>&rsquo;, the rule
-   simply becomes that all lines in the block must be kept together.
+   <pre>
+<!-- -->@page rotated { size: landscape }
+<!-- -->table { page: rotated; page-break-before: right }</pre>
+  </div>
 
-  <h3 id=allowed-pg-brk><span class=secno>2.4. </span> Allowed page breaks</h3>
+  <p> The &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
+   property works as follows: If a block box with inline content has a
+   &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
+   property that is different from the preceding block box with inline
+   content, then one or two page breaks are inserted between them, and the
+   boxes after the break are rendered on a page box of the named type. See <a
+   href="#forced-pg-brk">"Forced page breaks" below</a>.
+
+  <p> The &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
+   property does not inherit. However, if the &lsquo;<a href="#page"><code
+   class=property>page</code></a>&rsquo; value on an element is &lsquo;<code
+   class=css>auto</code>&rsquo;, then it is treated as having the same name
+   as its nearest ancestor with a non-auto value. When indicated on the root
+   element, the effective name is the empty string.
+
+  <p> Because a previous version of this specification indicated that the
+   &lsquo;<a href="#page"><code class=property>page</code></a>&rsquo;
+   property is inherited, an implementation that inherits the &lsquo;<a
+   href="#page"><code class=property>page</code></a>&rsquo; property and
+   treats &lsquo;<code class=css>auto</code>&rsquo; as always naming the
+   empty string remains conformant to CSS3 Paged Media. Therefore authors
+   should not explicitly specify the &lsquo;<code
+   class=css>auto</code>&rsquo; value on a descendant of an element with a
+   non-&lsquo;<code class=css>auto</code>&rsquo; &lsquo;<a href="#page"><code
+   class=property>page</code></a>&rsquo; value as the resulting behavior will
+   be unpredictable.
+
+  <p> Page names are case-sensitive identifiers. However the &lsquo;<code
+   class=css>auto</code>&rsquo; value, being a CSS keyword, is <a
+   href="http://www.w3.org/TR/CSS21/syndata.html#characters">case-insensitive</a>.
+   
+
+  <div class=example>
+   <p> In this example, the two tables are rendered on landscape pages
+    (indeed, on the same page, if they fit). The page type "narrow" is used
+    for the &lt;p&gt; after the second table, as the page properties for the
+    table element are no longer in effect:</p>
+
+   <pre>
+<!-- -->@page narrow { size: 9cm 18cm }
+<!-- -->@page rotated { size: landscape }
+<!-- -->div { page: narrow }
+<!-- -->table { page: rotated }</pre>
+
+   <p> with this document:</p>
+
+   <pre>
+<!-- -->&lt;div&gt;
+<!-- -->&lt;table&gt;...&lt;/table&gt;
+<!-- -->&lt;table&gt;...&lt;/table&gt;
+<!-- -->&lt;p&gt;This text is rendered on a 'narrow' page&lt;/p&gt;
+<!-- -->&lt;/div&gt;</pre>
+  </div>
+
+  <h2 id=breaking-rules><span class=secno>4. </span> Rules for Breaking</h2>
+
+  <h3 id=allowed-pg-brk><span class=secno>4.1. </span> Allowed page breaks</h3>
 
   <p>In the normal flow, page breaks may occur at the following places:
 
@@ -746,7 +764,7 @@
   <p> If that still does not lead to sufficient break points, rule C is
    dropped as well, to find still more break points.
 
-  <h3 id=forced-pg-brk><span class=secno>2.5. </span> Forced page breaks</h3>
+  <h3 id=forced-pg-brk><span class=secno>4.2. </span> Forced page breaks</h3>
 
   <p> A page break must occur at <a href="#brk-btw-blocks">(1)</a> if, among
    the'page-break-after' and &lsquo;<a href="#page-break-before"><code
@@ -776,7 +794,7 @@
    the used values of any adjoining &lsquo;<code
    class=property>margin-bottom</code>&rsquo; are set to zero.
 
-  <h3 id=best-pg-brk><span class=secno>2.6. </span> "Best" page breaks</h3>
+  <h3 id=best-pg-brk><span class=secno>4.3. </span> "Best" page breaks</h3>
 
   <p> CSS3 does <em>not</em> define which of a set of allowed page breaks
    must be used; except as defined earlier in the section, CSS3 does not
@@ -835,9 +853,9 @@
   </div>
   <!-- End section "Page Breaks" -->
 
-  <h2 id=conformance><span class=secno>3. </span> Conformance</h2>
+  <h2 id=conformance><span class=secno>5. </span> Conformance</h2>
 
-  <h3 id=conventions><span class=secno>3.1. </span> Document Conventions</h3>
+  <h3 id=conventions><span class=secno>5.1. </span> Document Conventions</h3>
 
   <p> Conformance requirements are expressed with a combination of
    descriptive assertions and RFC 2119 terminology. The key words “must”,
@@ -864,7 +882,7 @@
 
   <p class=note>Note, this is an informative note.
 
-  <h3 id=conformance-classes><span class=secno>3.2. </span>Conformance
+  <h3 id=conformance-classes><span class=secno>5.2. </span>Conformance
    Classes</h3>
 
   <p>Conformance to CSS Fragmentation is defined for three conformance
@@ -908,7 +926,7 @@
    other conformance requirements of style sheets as described in this
    module.
 
-  <h3 id=partial><span class=secno>3.3. </span> Partial Implementations</h3>
+  <h3 id=partial><span class=secno>5.3. </span> Partial Implementations</h3>
 
   <p> So that authors can exploit the forward-compatible parsing rules to
    assign fallback values, CSS renderers <strong>must</strong> treat as
@@ -921,7 +939,7 @@
    invalid (as unsupported values must be), CSS requires that the entire
    declaration be ignored.
 
-  <h3 id=experimental><span class=secno>3.4. </span> Experimental
+  <h3 id=experimental><span class=secno>5.4. </span> Experimental
    Implementations</h3>
 
   <p> To avoid clashes with future CSS features, the CSS2.1 specification
@@ -935,7 +953,7 @@
    vendor-prefixed syntax for such features, including those in W3C Working
    Drafts. This avoids incompatibilities with future changes in the draft.
 
-  <h3 id=testing><span class=secno>3.5. </span> Non-Experimental
+  <h3 id=testing><span class=secno>5.5. </span> Non-Experimental
    Implementations</h3>
 
   <p> Once a specification reaches the Candidate Recommendation stage,
@@ -957,7 +975,7 @@
    <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">
    public-css-testsuite@w3.org</a> mailing list.
 
-  <h3 id=cr-exit-criteria><span class=secno>3.6. </span> CR Exit Criteria</h3>
+  <h3 id=cr-exit-criteria><span class=secno>5.6. </span> CR Exit Criteria</h3>
 
   <p> For this specification to be advanced to Proposed Recommendation, there
    must be at least two independent, interoperable implementations of each
@@ -1098,34 +1116,34 @@
 
   <ul class=indexlist>
    <li>authoring tool, <a href="#authoring-tool"
-    title="authoring tool"><strong>3.2.</strong></a>
+    title="authoring tool"><strong>5.2.</strong></a>
 
-   <li>orphans, <a href="#orphans" title=orphans><strong>2.3.</strong></a>
+   <li>orphans, <a href="#orphans" title=orphans><strong>3.2.</strong></a>
 
-   <li>page, <a href="#page" title=page><strong>2.2.</strong></a>
+   <li>page, <a href="#page" title=page><strong>3.3.</strong></a>
 
    <li>page-break-after, <a href="#page-break-after"
-    title=page-break-after><strong>2.1.</strong></a>
+    title=page-break-after><strong>3.1.</strong></a>
 
    <li>page-break-before, <a href="#page-break-before"
-    title=page-break-before><strong>2.1.</strong></a>
+    title=page-break-before><strong>3.1.</strong></a>
 
    <li>page-break-inside, <a href="#page-break-inside"
-    title=page-break-inside><strong>2.1.</strong></a>
+    title=page-break-inside><strong>3.1.</strong></a>
 
    <li>pagination, <a href="#pagination"
     title=pagination><strong>1.</strong></a>
 
-   <li>renderer, <a href="#renderer" title=renderer><strong>3.2.</strong></a>
+   <li>renderer, <a href="#renderer" title=renderer><strong>5.2.</strong></a>
     
 
    <li>style sheet
     <ul>
      <li>as conformance class, <a href="#style-sheet"
-      title="style sheet, as conformance class"><strong>3.2.</strong></a>
+      title="style sheet, as conformance class"><strong>5.2.</strong></a>
     </ul>
 
-   <li>widows, <a href="#widows" title=widows><strong>2.3.</strong></a>
+   <li>widows, <a href="#widows" title=widows><strong>3.2.</strong></a>
   </ul>
   <!--end-index-->
 

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.src.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- Overview.src.html	24 Jan 2012 19:51:13 -0000	1.7
+++ Overview.src.html	24 Jan 2012 21:51:45 -0000	1.8
@@ -108,8 +108,13 @@
     repeated explicitly.
   </p>
 
-<h2 id="page-breaks">
-Page Breaks</h2>
+<h2 id="fragmentation-model">
+Fragmentation Model and Terminology</h2>
+
+
+
+<h3 id="page-breaks">
+Page Breaks</h3>
 
   <p>
     The following sections explain page breaking in CSS3 paged media. Five properties
@@ -126,6 +131,9 @@
     blank page if one exists, and onto the top of the subsequent page.
   </p>
 
+<h2 id="breaking-controls">
+Breaking Controls</h2>
+
 <h3 id="pg-br-before-after">
 Breaking before/after/inside elements: the 'page-break-before', 'page-break-after', and 'page-break-inside' properties
   </h3>
@@ -257,98 +265,6 @@
     flow of the root element. User agents may also apply these properties to other boxes.
   </p>
 
-<h3 id="using-named-pages">
-Using named pages: the 'page' property</h3>
-
-  <table class="propdef" summary="property definition">
-    <tr>
-      <th>Name:
-      <td><dfn id="page">page</dfn>
-    <tr>
-      <th>Value:
-      <td>auto | &lt;identifier&gt;
-    <tr>
-      <th>Initial:
-      <td>auto
-    <tr>
-      <th>Applies to:
-      <td>block-level elements
-    <tr>
-      <th>Inherited:
-      <td>no (but see prose)
-    <tr>
-      <th>Percentages:
-      <td>N/A
-    <tr>
-      <th>Media:
-      <td>paged
-    <tr>
-      <th>Computed value:
-      <td>specified value
-  </table>
-
-  <p>
-    The 'page' property is used to specify a particular
-    type of page where an element should be displayed.
-  </p>
-
-  <div class="example">
-      <p>This example will put all tables on a right-hand side landscape page (named "rotated"):</p>
-      <pre>
-@page rotated { size: landscape }
-table { page: rotated; page-break-before: right }
-      </pre>
-  </div>
-
-  <p>
-    The 'page' property works as follows: If a block box
-    with inline content has a 'page' property that is
-    different from the preceding block box with inline content, then one or two page
-    breaks are inserted between them, and the boxes after the break are rendered on
-    a page box of the named type. See <a href="#forced-pg-brk">"Forced page breaks" below</a>.
-  </p>
-  <p>
-    The 'page' property does not inherit. However, if the 'page' value on an element
-    is ''auto'', then it is treated as having the same name as its nearest ancestor
-    with a non-auto value. When indicated on the root element, the effective name is
-    the empty string.
-  </p>
-  <p>
-    Because a previous version of this specification indicated that the 'page' property
-    is inherited, an implementation that inherits the 'page' property and treats ''auto''
-    as always naming the empty string remains conformant to CSS3 Paged Media. Therefore
-    authors should not explicitly specify the ''auto'' value on a descendant of an element
-    with a non-''auto'' 'page' value as the resulting behavior will be unpredictable.
-  </p>
-
-  <p>
-    Page names are case-sensitive identifiers. However the ''auto'' value, being a CSS
-    keyword, is <a href="http://www.w3.org/TR/CSS21/syndata.html#characters">case-insensitive</a>.
-  </p>
-
-  <div class="example">
-
-    <p>
-      In this example, the two tables are rendered on landscape pages (indeed, on the
-      same page, if they fit). The page type "narrow" is used for the &lt;p&gt; after
-      the second table, as the page properties for the table element are no longer in
-      effect:</p>
-    <pre>
-@page narrow { size: 9cm 18cm }
-@page rotated { size: landscape }
-div { page: narrow }
-table { page: rotated }</pre>
-    <p>
-      with this document:
-    </p>
-    <pre>
-&lt;div&gt;
-&lt;table&gt;...&lt;/table&gt;
-&lt;table&gt;...&lt;/table&gt;
-&lt;p&gt;This text is rendered on a 'narrow' page&lt;/p&gt;
-&lt;/div&gt;</pre>
-  </div>
-
 <h3 id="breaks-inside">
 Breaks inside elements: 'orphans', 'widows'</h3>
 
@@ -439,6 +355,100 @@
     simply becomes that all lines in the block must be kept together.
   </p>
 
+<h3 id="using-named-pages">
+Using named pages: the 'page' property</h3>
+
+  <table class="propdef" summary="property definition">
+    <tr>
+      <th>Name:
+      <td><dfn id="page">page</dfn>
+    <tr>
+      <th>Value:
+      <td>auto | &lt;identifier&gt;
+    <tr>
+      <th>Initial:
+      <td>auto
+    <tr>
+      <th>Applies to:
+      <td>block-level elements
+    <tr>
+      <th>Inherited:
+      <td>no (but see prose)
+    <tr>
+      <th>Percentages:
+      <td>N/A
+    <tr>
+      <th>Media:
+      <td>paged
+    <tr>
+      <th>Computed value:
+      <td>specified value
+  </table>
+
+  <p>
+    The 'page' property is used to specify a particular
+    type of page where an element should be displayed.
+  </p>
+
+  <div class="example">
+    <p>This example will put all tables on a right-hand side landscape page (named "rotated"):</p>
+    <pre>
+<!-- -->@page rotated { size: landscape }
+<!-- -->table { page: rotated; page-break-before: right }</pre>
+  </div>
+
+  <p>
+    The 'page' property works as follows: If a block box
+    with inline content has a 'page' property that is
+    different from the preceding block box with inline content, then one or two page
+    breaks are inserted between them, and the boxes after the break are rendered on
+    a page box of the named type. See <a href="#forced-pg-brk">"Forced page breaks" below</a>.
+  </p>
+  <p>
+    The 'page' property does not inherit. However, if the 'page' value on an element
+    is ''auto'', then it is treated as having the same name as its nearest ancestor
+    with a non-auto value. When indicated on the root element, the effective name is
+    the empty string.
+  </p>
+  <p>
+    Because a previous version of this specification indicated that the 'page' property
+    is inherited, an implementation that inherits the 'page' property and treats ''auto''
+    as always naming the empty string remains conformant to CSS3 Paged Media. Therefore
+    authors should not explicitly specify the ''auto'' value on a descendant of an element
+    with a non-''auto'' 'page' value as the resulting behavior will be unpredictable.
+  </p>
+
+  <p>
+    Page names are case-sensitive identifiers. However the ''auto'' value, being a CSS
+    keyword, is <a href="http://www.w3.org/TR/CSS21/syndata.html#characters">case-insensitive</a>.
+  </p>
+
+  <div class="example">
+
+    <p>
+      In this example, the two tables are rendered on landscape pages (indeed, on the
+      same page, if they fit). The page type "narrow" is used for the &lt;p&gt; after
+      the second table, as the page properties for the table element are no longer in
+      effect:</p>
+    <pre>
+<!-- -->@page narrow { size: 9cm 18cm }
+<!-- -->@page rotated { size: landscape }
+<!-- -->div { page: narrow }
+<!-- -->table { page: rotated }</pre>
+    <p>
+      with this document:
+    </p>
+    <pre>
+<!-- -->&lt;div&gt;
+<!-- -->&lt;table&gt;...&lt;/table&gt;
+<!-- -->&lt;table&gt;...&lt;/table&gt;
+<!-- -->&lt;p&gt;This text is rendered on a 'narrow' page&lt;/p&gt;
+<!-- -->&lt;/div&gt;</pre>
+  </div>
+
+<h2 id="breaking-rules">
+Rules for Breaking</h2>
+
 <h3 id="allowed-pg-brk">
 Allowed page breaks</h3>
 
Received on Tuesday, 24 January 2012 21:51:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:26:09 UTC