- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 24 Jan 2012 19:43:23 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-break
In directory hutz:/tmp/cvs-serv7823
Modified Files:
Overview.html Overview.src.html
Log Message:
Reformat source, part II
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- Overview.html 24 Jan 2012 19:34:16 -0000 1.4
+++ Overview.html 24 Jan 2012 19:43:21 -0000 1.5
@@ -139,61 +139,49 @@
<li><a href="#values"><span class=secno>1.2. </span>Values</a>
</ul>
- <li><a href="#fragmentation-model"><span class=secno>2.
- </span>Fragmentation Model and Terminology</a>
-
- <li><a href="#page-breaks"><span class=secno>3. </span>Page Breaks</a>
-
- <li><a href="#breaking-controls"><span class=secno>4. </span>Controlling
- Breaks</a>
+ <li><a href="#page-breaks"><span class=secno>2. </span>Page Breaks</a>
<ul class=toc>
- <li><a href="#pg-br-before-after"><span class=secno>4.1. </span> Break
- before/after elements: <span class=property>‘<code
- class=property>page-break-before</code>’</span>, <span
- class=property>‘<code
- class=property>page-break-after</code>’</span>, <span
- class=property>‘<code
- class=property>page-break-inside</code>’</span> </a>
+ <li><a href="#pg-br-before-after"><span class=secno>2.1. </span> Break
+ before/after elements: ‘<code
+ class=property>page-break-before</code>’, ‘<code
+ class=property>page-break-after</code>’, ‘<code
+ class=property>page-break-inside</code>’ </a>
- <li><a href="#using-named-pages"><span class=secno>4.2. </span>Using
+ <li><a href="#using-named-pages"><span class=secno>2.2. </span>Using
named pages: ‘<code class=property>page</code>’</a>
- <li><a href="#breaks-inside"><span class=secno>4.3. </span>Breaks inside
+ <li><a href="#breaks-inside"><span class=secno>2.3. </span>Breaks inside
elements: ‘<code class=property>orphans</code>’,
‘<code class=property>widows</code>’</a>
- </ul>
- <li><a href="#breaking-rules"><span class=secno>5. </span>Rules for
- Breaking</a>
- <ul class=toc>
- <li><a href="#allowed-pg-brk"><span class=secno>5.1. </span>Allowed page
+ <li><a href="#allowed-pg-brk"><span class=secno>2.4. </span>Allowed page
breaks</a>
- <li><a href="#forced-pg-brk"><span class=secno>5.2. </span>Forced page
+ <li><a href="#forced-pg-brk"><span class=secno>2.5. </span>Forced page
breaks</a>
- <li><a href="#best-pg-brk"><span class=secno>5.3. </span>"Best" page
+ <li><a href="#best-pg-brk"><span class=secno>2.6. </span>"Best" page
breaks</a>
</ul>
- <li><a href="#conformance"><span class=secno>6. </span>Conformance</a>
+ <li><a href="#conformance"><span class=secno>3. </span>Conformance</a>
<ul class=toc>
- <li><a href="#conventions"><span class=secno>6.1. </span>Document
+ <li><a href="#conventions"><span class=secno>3.1. </span>Document
Conventions</a>
- <li><a href="#conformance-classes"><span class=secno>6.2.
+ <li><a href="#conformance-classes"><span class=secno>3.2.
</span>Conformance Classes</a>
- <li><a href="#partial"><span class=secno>6.3. </span> Partial
+ <li><a href="#partial"><span class=secno>3.3. </span> Partial
Implementations</a>
- <li><a href="#experimental"><span class=secno>6.4. </span> Experimental
+ <li><a href="#experimental"><span class=secno>3.4. </span> Experimental
Implementations</a>
- <li><a href="#testing"><span class=secno>6.5. </span> Non-Experimental
+ <li><a href="#testing"><span class=secno>3.5. </span> Non-Experimental
Implementations</a>
- <li><a href="#cr-exit-criteria"><span class=secno>6.6. </span> CR Exit
+ <li><a href="#cr-exit-criteria"><span class=secno>3.6. </span> CR Exit
Criteria</a>
</ul>
@@ -217,24 +205,45 @@
<p><em>This section is not normative.</em>
- <p> In paged media (e.g., paper, transparencies, photo album pages, pages
- displayed on computer screens as printed output simulations), as opposed
- to <a href="/TR/CSS2/media.html#continuous-media-group"> continuous
- media</a>, the content of the document is split into one or more discrete
- display surfaces. In order to avoid awkward breaks (such as halfway
- through a line of text), the layout engine must be able to shift around
- content that would fall across the page break. This process is called <dfn
- id=pagination>pagination</dfn>.
+ <p> Paged media (e.g., paper, transparencies, photo album pages, pages
+ displayed on computer screens as printed output simulations) differ from
+ <a href="/TR/CSS2/media.html#continuous-media-group"> continuous media</a>
+ in that the content of the document is split into one or more discrete
+ static display surfaces. To handle pages, CSS3 Paged Media describes how:
- <p> In CSS, in addition to paged media, certain layout features such as
- regions [[CSS3REGION]] and multi-column layout [[CSS3MULTICOL]] create a
- similarly fragmented environment. This module explains how content breaks
- across fragment containers such as pages and columns and how such breaks
- can be controlled by the author.
+ <ul>
+ <li><a href="#page-breaks">page breaks</a> are created and avoided;
+
+ <li>the page properties such as size, orientation, margins, border, and
+ padding are specified;
+
+ <li>headers and footers are established within the page margins;
+
+ <li>content such as page counters are placed in the headers and footers;
+ and
+
+ <li>orphans and widows can be controlled.
+ </ul>
+
+ <p> This module defines a <a href="#page-model">page model</a> that
+ specifies how a document is formatted within a rectangular area, called
+ the <a href="#page-box-page-rule"> page box</a>, that has finite width and
+ height.
+
+ <p> Although CSS3 does not specify how user agents transfer page boxes to
+ sheets, it does include certain mechanisms for telling user agents about
+ the intended page sheet <a href="#page-size">size and orientation</a>. In
+ the general case, CSS3 assumes that one page box will be transferred to
+ one surface of similar size.
+
+ <p> All properties defined in this specification also accept the <a
+ href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">
+ inherit</a> keyword as their value, but for readability it has not been
+ listed explicitly.
<h3 id=placement><span class=secno>1.1. </span>Module Interactions</h3>
- <p>This module replaces and extends the pagination controls defined in <a
+ <p> This module replaces and extends the pagination controls defined in <a
href="#CSS21" rel=biblioentry>[CSS21]<!--{{CSS21}}--></a> <a
href="http://www.w3.org/TR/CSS21/page.html#page-breaks">section 13.3</a>
and in <a href="#CSS3PAGE"
@@ -260,15 +269,11 @@
inherit</a> keyword as their property value. For readability it has not
been repeated explicitly.
- <h2 id=fragmentation-model><span class=secno>2. </span>Fragmentation Model
- and Terminology</h2>
-
- <h2 id=page-breaks><span class=secno>3. </span>Page Breaks</h2>
+ <h2 id=page-breaks><span class=secno>2. </span>Page Breaks</h2>
<p> The following sections explain page breaking in CSS3 paged media. Five
- properties indicate where the user agent <em class=RFC2119>MAY</em> or <em
- class=RFC2119>SHOULD</em> break pages, and on what page (left or right)
- the subsequent content <em class=RFC2119> SHOULD</em> resume. Each page
+ properties indicate where the user agent may or should break pages, and on
+ what page (left or right) the subsequent content should resume. Each page
break ends layout in the current <a href="#page-box">page box</a> and
causes remaining pieces of the document tree to be laid out in a new page
box.
@@ -279,15 +284,13 @@
the page, through an ensuing blank page if one exists, and onto the top of
the subsequent page.
- <h2 id=breaking-controls><span class=secno>4. </span>Controlling Breaks</h2>
-
- <h3 id=pg-br-before-after><span class=secno>4.1. </span> Break before/after
- elements: <span class=property>‘<a href="#page-break-before"><code
- class=property>page-break-before</code></a>’</span>, <span
- class=property>‘<a href="#page-break-after"><code
- class=property>page-break-after</code></a>’</span>, <span
- class=property>‘<a href="#page-break-inside"><code
- class=property>page-break-inside</code></a>’</span></h3>
+ <h3 id=pg-br-before-after><span class=secno>2.1. </span> Break before/after
+ elements: ‘<a href="#page-break-before"><code
+ class=property>page-break-before</code></a>’, ‘<a
+ href="#page-break-after"><code
+ class=property>page-break-after</code></a>’, ‘<a
+ href="#page-break-inside"><code
+ class=property>page-break-inside</code></a>’</h3>
<table class=propdef summary="property definition">
<tbody>
@@ -424,16 +427,16 @@
<dl>
<dt>auto
- <dd>Neither force nor forbid a page break before / after / inside the
+ <dd> Neither force nor forbid a page break before / after / inside the
generated box.
<dt>always
- <dd>Always force a page break before / after the generated box.
+ <dd> Always force a page break before / after the generated box.
<dt>avoid
- <dd>Avoid a page break before / after / inside the generated box.
+ <dd> Avoid a page break before / after / inside the generated box.
<dt>left
@@ -447,22 +450,17 @@
</dl>
<p> A potential page break location is typically under the influence of the
- parent element's <span class=property>‘<a
- href="#page-break-inside"><code
- class=property>page-break-inside</code></a>’</span> property, the
- <span class=property> ‘<a href="#page-break-after"><code
- class=property>page-break-after</code></a>’</span> property of the
- preceding element, and the <span class=property> ‘<a
- href="#page-break-before"><code
- class=property>page-break-before</code></a>’</span> property of the
- following element. When these properties have values other than <span
- class=css>‘<code class=property>auto</code>’</span>, the
- values <span class=css>‘<code
- class=property>always</code>’</span>, <span class=css>‘<code
- class=property>left</code>’</span>, and <span class=css>
- ‘<code class=property>right</code>’</span> take precedence
- over <span class=css>‘<code
- class=property>avoid</code>’</span>. See the section on <a
+ parent element's ‘<a href="#page-break-inside"><code
+ class=property>page-break-inside</code></a>’ property, the ‘<a
+ href="#page-break-after"><code
+ class=property>page-break-after</code></a>’ property of the
+ preceding element, and the ‘<a href="#page-break-before"><code
+ class=property>page-break-before</code></a>’ property of the
+ following element. When these properties have values other than
+ ‘<code class=css>auto</code>’, the values ‘<code
+ class=css>always</code>’, ‘<code class=css>left</code>’,
+ and ‘<code class=css>right</code>’ take precedence over
+ ‘<code class=property>avoid</code>’. See the section on <a
href="#allowed-pg-brk">allowed page breaks</a> for the exact rules on how
these properties affect page breaks.
@@ -475,7 +473,7 @@
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>4.2. </span>Using named pages:
+ <h3 id=using-named-pages><span class=secno>2.2. </span>Using named pages:
‘<a href="#page"><code class=property>page</code></a>’</h3>
<table class=propdef summary="property definition">
@@ -521,10 +519,9 @@
<td>specified value
</table>
- <p> The <span class=property>‘<a href="#page"><code
- class=property>page</code></a>’</span> property is used to specify a
- particular type of page where an element <em class=RFC2119>SHOULD</em> be
- displayed.
+ <p> The ‘<a href="#page"><code class=property>page</code></a>’
+ 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
@@ -533,16 +530,15 @@
<pre>
@page rotated { size: landscape }
table { page: rotated; page-break-before: right }
- </pre>
+ </pre>
</div>
- <p> The <span class=property>‘<a href="#page"><code
- class=property>page</code></a>’</span> property works as follows: If
- a block box with inline content has a <span class=property>‘<a
- href="#page"><code class=property>page</code></a>’</span> 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
+ <p> The ‘<a href="#page"><code class=property>page</code></a>’
+ property works as follows: If a block box with inline content has a
+ ‘<a href="#page"><code class=property>page</code></a>’
+ 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 ‘<a href="#page"><code class=property>page</code></a>’
@@ -579,19 +575,19 @@
@page narrow { size: 9cm 18cm }
@page rotated { size: landscape }
div { page: narrow }
-table { page: rotated }
-</pre>
- with this document:
+table { page: rotated }</pre>
+
+ <p> with this document:</p>
+
<pre>
<div>
<table>...</table>
<table>...</table>
<p>This text is rendered on a 'narrow' page</p>
-</div>
-</pre>
+</div></pre>
</div>
- <h3 id=breaks-inside><span class=secno>4.3. </span>Breaks inside elements:
+ <h3 id=breaks-inside><span class=secno>2.3. </span>Breaks inside elements:
‘<a href="#orphans"><code class=property>orphans</code></a>’,
‘<a href="#widows"><code class=property>widows</code></a>’</h3>
@@ -681,33 +677,29 @@
<td>specified value
</table>
- <p> The <span class=property>‘<a href="#orphans"><code
- class=property>orphans</code></a>’</span> property specifies the
- minimum number of line boxes in a block element that <em
- class=RFC2119>MUST</em> be left at the bottom of a page. The <span
- class=property>‘<a href="#widows"><code
- class=property>widows</code></a>’</span> property specifies the
- minimum number of line boxes of a block element that <em
- class=RFC2119>MUST</em> be left at the top of a page. Examples of how they
- are used to control page breaks are given below.
+ <p> The ‘<a href="#orphans"><code
+ class=property>orphans</code></a>’ property specifies the minimum
+ number of line boxes in a block element that must be left at the bottom of
+ a page. The ‘<a href="#widows"><code
+ class=property>widows</code></a>’ 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 ‘<a
href="#orphans"><code class=property>orphans</code></a>’ and
‘<a href="#widows"><code class=property>widows</code></a>’.
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>.
+ href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.
<p> If a block contains fewer lines than the value of ‘<a
href="#widows"><code class=property>widows</code></a>’ or ‘<a
href="#orphans"><code class=property>orphans</code></a>’, the rule
simply becomes that all lines in the block must be kept together.
- <h2 id=breaking-rules><span class=secno>5. </span>Rules for Breaking</h2>
-
- <h3 id=allowed-pg-brk><span class=secno>5.1. </span>Allowed page breaks</h3>
+ <h3 id=allowed-pg-brk><span class=secno>2.4. </span>Allowed page breaks</h3>
- <p>In the normal flow, page breaks <em class=RFC2119>may</em> occur at the
- following places:
+ <p>In the normal flow, page breaks may occur at the following places:
<ol>
<li id=brk-btw-blocks> In the vertical margin between sibling block boxes
@@ -733,19 +725,17 @@
href="#page-break-before"><code
class=property>page-break-before</code></a>’ properties of all the
elements generating boxes that meet at this margin allow it, which is
- when at least one of them has the value <span class=css>‘<code
- class=property>always</code>’</span>, <span class=css>‘<code
- class=property>left</code>’</span>, or <span class=css>‘<code
- class=property>right</code>’</span>, or when all of them are <span
- class=css>‘<code class=property>auto</code>’</span>.
+ when at least one of them has the value ‘<code
+ class=css>always</code>’, ‘<code
+ class=css>left</code>’, or ‘<code
+ class=css>right</code>’, or when all of them are ‘<code
+ class=css>auto</code>’.
- <li> <strong>Rule B:</strong> However, if all of them are <span
- class=css>‘<code class=property>auto</code>’</span> and a
- common ancestor of all the elements has a <span class=property>‘<a
- href="#page-break-inside"><code
- class=property>page-break-inside</code></a>’</span> value of <span
- class=css>‘<code class=property>avoid</code>’</span>, then
- breaking here is not allowed.
+ <li> <strong>Rule B:</strong> However, if all of them are ‘<code
+ class=css>auto</code>’ and a common ancestor of all the elements
+ has a ‘<a href="#page-break-inside"><code
+ class=property>page-break-inside</code></a>’ value of ‘<code
+ class=css>avoid</code>’, then breaking here is not allowed.
<li> <strong>Rule C:</strong> Breaking at <a href="#brk-btw-lines">(2)</a>
is allowed only if the number of line boxes between the break and the
@@ -772,17 +762,15 @@
<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>5.2. </span>Forced page breaks</h3>
+ <h3 id=forced-pg-brk><span class=secno>2.5. </span>Forced page breaks</h3>
- <p> A page break <em class=RFC2119>MUST</em> occur at <a
- href="#brk-btw-blocks">(1)</a> if, among the'page-break-after' and
- ‘<a href="#page-break-before"><code
+ <p> A page break must occur at <a href="#brk-btw-blocks">(1)</a> if, among
+ the'page-break-after' and ‘<a href="#page-break-before"><code
class=property>page-break-before</code></a>’ properties of all the
elements generating boxes that meet at this margin, there is at least one
- with the value <span class=css>‘<code
- class=property>always</code>’</span>, <span class=css>‘<code
- class=property>left</code>’</span>, or <span class=css> ‘<code
- class=property>right</code>’</span>.
+ with the value ‘<code class=css>always</code>’, ‘<code
+ class=css>left</code>’, or ‘<code
+ class=css>right</code>’.
<p> When multiple ‘<a href="#page-break-before"><code
class=property>page-break-before</code></a>’ and/or ‘<a
@@ -795,23 +783,23 @@
‘<code class=property>left</code>’ values to position ensuing
content on a right- or left-facing page.
- <p> A page break <em class=RFC2119>MUST</em> also occur at <a
- href="#brk-btw-blocks">(1)</a> if the last line box above this margin and
- the first one below it do not have the same value for ‘<a
- href="#page"><code class=property>page</code></a>’.
+ <p> A page break must also occur at <a href="#brk-btw-blocks">(1)</a> if
+ the last line box above this margin and the first one below it do not have
+ the same value for ‘<a href="#page"><code
+ class=property>page</code></a>’.
<p> When a forced page break occurs at <a href="#brk-btw-blocks">(1)</a>,
the used values of any adjoining ‘<code
class=property>margin-bottom</code>’ are set to zero.
- <h3 id=best-pg-brk><span class=secno>5.3. </span>"Best" page breaks</h3>
+ <h3 id=best-pg-brk><span class=secno>2.6. </span>"Best" page breaks</h3>
- <p> CSS3 does <em>not</em> define which of a set of allowed page breaks <em
- class=RFC2119> MUST</em> be used; except as defined earlier in the
- section, CSS3 does not forbid a user agent to break at every possible
- break point, or to not break at all. But CSS3 does recommend that user
- agents observe the following guidelines (while recognizing that they are
- sometimes contradictory):
+ <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
+ forbid a user agent to break at every possible break point, or to not
+ break at all. But CSS3 does recommend that user agents observe the
+ following guidelines (while recognizing that they are sometimes
+ contradictory):
<ul>
<li>Break as few times as possible.
@@ -823,58 +811,54 @@
</ul>
<div class=example>
- <p> Suppose, for example, that the style sheet contains <span
- class=css>‘<code class=css>orphans : 4</code>’</span>, <span
- class=css>‘<code class=css>widows : 2</code>’</span>, and
- there are 20 lines (line boxes) available at the bottom of the current
- page, and the next block in normal flow is considered for placement:</p>
+ <p> Suppose, for example, that the style sheet contains ‘<code
+ class=css>orphans : 4</code>’, ‘<code class=css>widows :
+ 2</code>’, and there are 20 lines (line boxes) available at the
+ bottom of the current page, and the next block in normal flow is
+ considered for placement:</p>
<ul>
- <li> If the block contains 20 line boxes or fewer, it <em
- class=RFC2119>SHOULD</em> be placed on the current page.
+ <li> If the block contains 20 line boxes or fewer, it should be placed on
+ the current page.
<li> If the block contains 21 or 22 line boxes, the second part of the
- paragraph <em class=RFC2119>MUST</em> not violate the <span
- class=property>‘<a href="#widows"><code
- class=property>widows</code></a>’</span> constraint, and so the
- second part <em class=RFC2119>MUST</em> contain at least two line boxes;
- likewise the first part <em class=RFC2119>MUST</em> contain at least
- four line boxes.
+ paragrap must not violate the ‘<a href="#widows"><code
+ class=property>widows</code></a>’ constraint, and so the second
+ part must contain at least two line boxes; likewise the first part must
+ contain at least four line boxes.
- <li> If the block contains 23 line boxes or more, the first part <em
- class=RFC2119> SHOULD</em> contain 20 lines and the second part the
- remaining lines. (But if any part of the block is placed on the current
- page, that part <em class=RFC2119>MUST</em> contain at least four line
- boxes and the second part at least two line boxes.)
+ <li> If the block contains 23 line boxes or more, the first part should
+ contain 20 lines and the second part the remaining lines. (But if any
+ part of the block is placed on the current page, that part must contain
+ at least four line boxes and the second part at least two line boxes.)
</ul>
- <p> Now suppose that <span class=property>‘<a href="#orphans"><code
- class=property>orphans</code></a>’</span> is <span
- class=css>‘<code class=css>10</code>’</span>, <span
- class=property>‘<a href="#widows"><code
- class=property>widows</code></a>’</span> is <span
- class=css>‘<code class=css>20</code>’</span>, and there are 8
- lines available at the bottom of the current page:</p>
+ <p> Now suppose that ‘<a href="#orphans"><code
+ class=property>orphans</code></a>’ is ‘<code
+ class=css>10</code>’, ‘<a href="#widows"><code
+ class=property>widows</code></a>’ is ‘<code
+ class=css>20</code>’, and there are 8 lines available at the bottom
+ of the current page:</p>
<ul>
- <li> If the block contains 8 lines or fewer, it <em
- class=RFC2119>SHOULD</em> be placed on the current page.
+ <li> If the block contains 8 lines or fewer, it should be placed on the
+ current page.
- <li> If the block contains 9 lines or more, it <em class=RFC2119>MAY
- NOT</em> be split (that would violate the orphan constraint), so it <em
- class=RFC2119>MUST</em> move as a block to the next page.
+ <li> If the block contains 9 lines or more, it may NOT be split (that
+ would violate the orphan constraint), so it must move as a block to the
+ next page.
</ul>
</div>
<!-- End section "Page Breaks" -->
- <h2 id=conformance><span class=secno>6. </span>Conformance</h2>
+ <h2 id=conformance><span class=secno>3. </span>Conformance</h2>
- <h3 id=conventions><span class=secno>6.1. </span>Document Conventions</h3>
+ <h3 id=conventions><span class=secno>3.1. </span>Document Conventions</h3>
<p> Conformance requirements are expressed with a combination of
- descriptive assertions and RFC 2119 terminology. The key words “MUST”,
- “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
- “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and
+ descriptive assertions and RFC 2119 terminology. The key words “must”,
+ “must NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
+ “should”, “should NOT”, “RECOMMENDED”, “may”, and
“OPTIONAL” in the normative parts of this document are to be
interpreted as described in RFC 2119. However, for readability, these
words do not appear in all uppercase letters in this specification.
@@ -896,7 +880,7 @@
<p class=note>Note, this is an informative note.
- <h3 id=conformance-classes><span class=secno>6.2. </span>Conformance
+ <h3 id=conformance-classes><span class=secno>3.2. </span>Conformance
Classes</h3>
<p>Conformance to CSS Fragmentation is defined for three conformance
@@ -940,7 +924,7 @@
other conformance requirements of style sheets as described in this
module.
- <h3 id=partial><span class=secno>6.3. </span> Partial Implementations</h3>
+ <h3 id=partial><span class=secno>3.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
@@ -953,7 +937,7 @@
invalid (as unsupported values must be), CSS requires that the entire
declaration be ignored.
- <h3 id=experimental><span class=secno>6.4. </span> Experimental
+ <h3 id=experimental><span class=secno>3.4. </span> Experimental
Implementations</h3>
<p> To avoid clashes with future CSS features, the CSS2.1 specification
@@ -967,7 +951,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>6.5. </span> Non-Experimental
+ <h3 id=testing><span class=secno>3.5. </span> Non-Experimental
Implementations</h3>
<p> Once a specification reaches the Candidate Recommendation stage,
@@ -989,7 +973,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>6.6. </span> CR Exit Criteria</h3>
+ <h3 id=cr-exit-criteria><span class=secno>3.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
@@ -1110,34 +1094,31 @@
<ul class=indexlist>
<li>authoring tool, <a href="#authoring-tool"
- title="authoring tool"><strong>6.2.</strong></a>
+ title="authoring tool"><strong>3.2.</strong></a>
- <li>orphans, <a href="#orphans" title=orphans><strong>4.3.</strong></a>
+ <li>orphans, <a href="#orphans" title=orphans><strong>2.3.</strong></a>
- <li>page, <a href="#page" title=page><strong>4.2.</strong></a>
+ <li>page, <a href="#page" title=page><strong>2.2.</strong></a>
<li>page-break-after, <a href="#page-break-after"
- title=page-break-after><strong>4.1.</strong></a>
+ title=page-break-after><strong>2.1.</strong></a>
<li>page-break-before, <a href="#page-break-before"
- title=page-break-before><strong>4.1.</strong></a>
+ title=page-break-before><strong>2.1.</strong></a>
<li>page-break-inside, <a href="#page-break-inside"
- title=page-break-inside><strong>4.1.</strong></a>
-
- <li>pagination, <a href="#pagination"
- title=pagination><strong>1.</strong></a>
+ title=page-break-inside><strong>2.1.</strong></a>
- <li>renderer, <a href="#renderer" title=renderer><strong>6.2.</strong></a>
+ <li>renderer, <a href="#renderer" title=renderer><strong>3.2.</strong></a>
<li>style sheet
<ul>
<li>as conformance class, <a href="#style-sheet"
- title="style sheet, as conformance class"><strong>6.2.</strong></a>
+ title="style sheet, as conformance class"><strong>3.2.</strong></a>
</ul>
- <li>widows, <a href="#widows" title=widows><strong>4.3.</strong></a>
+ <li>widows, <a href="#widows" title=widows><strong>2.3.</strong></a>
</ul>
<!--end-index-->
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.src.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- Overview.src.html 24 Jan 2012 19:34:16 -0000 1.5
+++ Overview.src.html 24 Jan 2012 19:43:21 -0000 1.6
@@ -113,9 +113,9 @@
<p>
The following sections explain page breaking in CSS3 paged media. Five properties
- indicate where the user agent <em class="RFC2119">MAY</em> or <em class="RFC2119">SHOULD</em>
- break pages, and on what page (left or right) the subsequent content <em class="RFC2119">
- SHOULD</em> resume. Each page break ends layout in the current <a href="#page-box">page
+ indicate where the user agent may or should break pages, and on what page
+ (left or right) the subsequent content should resume. Each page break ends
+ layout in the current <a href="#page-box">page
box</a> and causes remaining pieces of the document tree to be laid out
in a new page box.
</p>
@@ -127,8 +127,8 @@
</p>
<h3 id="pg-br-before-after">
- Break before/after elements: <span class="property">'page-break-before'</span>,
- <span class="property">'page-break-after'</span>, <span class="property">'page-break-inside'</span>
+ Break before/after elements: 'page-break-before',
+ 'page-break-after', 'page-break-inside'
</h3>
<table class="propdef" summary="property definition">
@@ -287,8 +287,8 @@
</table>
<p>
- The <span class="property">'page'</span> property is used to specify a particular
- type of page where an element <em class="RFC2119">SHOULD</em> be displayed.
+ The 'page' property is used to specify a particular
+ type of page where an element should be displayed.
</p>
<div class="example">
@@ -300,8 +300,8 @@
</div>
<p>
- The <span class="property">'page'</span> property works as follows: If a block box
- with inline content has a <span class="property">'page'</span> property that is
+ 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>.
@@ -420,17 +420,16 @@
</table>
<p>
- The <span class="property">'orphans'</span> property specifies the minimum number
- of line boxes in a block element that <em class="RFC2119">MUST</em> be left at the
- bottom of a page. The <span class="property">'widows'</span> property specifies
- the minimum number of line boxes of a block element that <em class="RFC2119">MUST</em>
- be left at the top of a page. Examples of how they are used to control page breaks
- are given below.
+ The 'orphans' property specifies the minimum number of line boxes in
+ a block element that must be left at the bottom of a page. The 'widows'
+ 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>
<p>
Only positive integers are allowed as values of 'orphans' and 'widows'. 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>.
+ 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>
<p>
If a block contains fewer lines than the value of 'widows' or 'orphans', the rule
@@ -439,7 +438,7 @@
<h3 id="allowed-pg-brk">Allowed page breaks</h3>
- <p>In the normal flow, page breaks <em class="RFC2119">may</em> occur at the following places:</p>
+ <p>In the normal flow, page breaks may occur at the following places:</p>
<ol>
<li id="brk-btw-blocks">
@@ -462,13 +461,13 @@
<strong>Rule A:</strong> Breaking at <a href="#brk-btw-blocks">(1)</a> is allowed
only if the 'page-break-after' and 'page-break-before' properties of all the elements
generating boxes that meet at this margin allow it, which is when at least one of
- them has the value 'always'</span>, 'left'</span>,
- or 'right'</span>, or when all of them are 'auto'</span>.
+ them has the value ''always'', ''left'',
+ or ''right'', or when all of them are ''auto''.
</li>
<li>
- <strong>Rule B:</strong> However, if all of them are 'auto'</span>
- and a common ancestor of all the elements has a <span class="property">'page-break-inside'</span>
- value of 'avoid'</span>, then breaking here is not allowed.
+ <strong>Rule B:</strong> However, if all of them are ''auto''
+ and a common ancestor of all the elements has a 'page-break-inside'
+ value of ''avoid'', then breaking here is not allowed.
</li>
<li>
<strong>Rule C:</strong> Breaking at <a href="#brk-btw-lines">(2)</a> is allowed
@@ -496,11 +495,11 @@
<h3 id="forced-pg-brk">Forced page breaks</h3>
<p>
- A page break <em class="RFC2119">MUST</em> occur at <a href="#brk-btw-blocks">(1)</a>
+ A page break must occur at <a href="#brk-btw-blocks">(1)</a>
if, among the'page-break-after' and 'page-break-before' properties of all the elements
generating boxes that meet at this margin, there is at least one with the value
- 'always'</span>, 'left'</span>, or
- 'right'</span>.
+ ''always'', ''left'', or
+ ''right''.
</p>
<p>
When multiple 'page-break-before' and/or 'page-break-after' properties with values
@@ -510,7 +509,7 @@
values to position ensuing content on a right- or left-facing page.
</p>
<p>
- A page break <em class="RFC2119">MUST</em> also occur at <a href="#brk-btw-blocks">(1)</a>
+ A page break must also occur at <a href="#brk-btw-blocks">(1)</a>
if the last line box above this margin and the first one below it do not have the
same value for 'page'.
</p>
@@ -522,8 +521,8 @@
<h3 id="best-pg-brk">"Best" page breaks</h3>
<p>
- CSS3 does <em>not</em> define which of a set of allowed page breaks <em class="RFC2119">
- MUST</em> be used; except as defined earlier in the section, CSS3 does not forbid
+ 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 forbid
a user agent to break at every possible break point, or to not break at all. But
CSS3 does recommend that user agents observe the following guidelines (while recognizing
that they are sometimes contradictory):</p>
@@ -534,43 +533,43 @@
</ul>
<div class="example">
<p>
- Suppose, for example, that the style sheet contains 'orphans : 4'</span>,
- 'widows : 2'</span>, and there are 20 lines (line boxes) available
+ Suppose, for example, that the style sheet contains ''orphans : 4'',
+ ''widows : 2'', and there are 20 lines (line boxes) available
at the bottom of the current page, and the next block in normal flow is considered
for placement:
</p>
<ul>
<li>
- If the block contains 20 line boxes or fewer, it <em class="RFC2119">SHOULD</em>
+ If the block contains 20 line boxes or fewer, it should
be placed on the current page.
</li>
<li>
- If the block contains 21 or 22 line boxes, the second part of the paragraph <em
- class="RFC2119">MUST</em> not violate the <span class="property">'widows'</span>
- constraint, and so the second part <em class="RFC2119">MUST</em> contain at least
- two line boxes; likewise the first part <em class="RFC2119">MUST</em> contain at
+ If the block contains 21 or 22 line boxes, the second part of the paragrap
+ must not violate the 'widows'
+ constraint, and so the second part must contain at least
+ two line boxes; likewise the first part must contain at
least four line boxes.
</li>
<li>
- If the block contains 23 line boxes or more, the first part <em class="RFC2119">
- SHOULD</em> contain 20 lines and the second part the remaining lines. (But if any
- part of the block is placed on the current page, that part <em class="RFC2119">MUST</em>
+ If the block contains 23 line boxes or more, the first part should contain
+ 20 lines and the second part the remaining lines. (But if any
+ part of the block is placed on the current page, that part must
contain at least four line boxes and the second part at least two line boxes.)
</li>
</ul>
<p>
- Now suppose that <span class="property">'orphans'</span> is '10'</span>,
- <span class="property">'widows'</span> is '20'</span>, and there
+ Now suppose that 'orphans' is ''10'',
+ 'widows' is ''20'', and there
are 8 lines available at the bottom of the current page:
</p>
<ul>
<li>
- If the block contains 8 lines or fewer, it <em class="RFC2119">SHOULD</em> be placed
+ If the block contains 8 lines or fewer, it should be placed
on the current page.
</li>
<li>
- If the block contains 9 lines or more, it <em class="RFC2119">MAY NOT</em> be split
- (that would violate the orphan constraint), so it <em class="RFC2119">MUST</em>
+ If the block contains 9 lines or more, it may NOT be split
+ (that would violate the orphan constraint), so it must
move as a block to the next page.
</li>
</ul>
@@ -582,8 +581,8 @@
<h3 id="conventions">Document Conventions</h3>
<p>
Conformance requirements are expressed with a combination of descriptive assertions
- and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”,
- “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the
+ and RFC 2119 terminology. The key words “must”, “must NOT”, “REQUIRED”, “SHALL”,
+ “SHALL NOT”, “should”, “should NOT”, “RECOMMENDED”, “may”, and “OPTIONAL” in the
normative parts of this document are to be interpreted as described in RFC 2119.
However, for readability, these words do not appear in all uppercase letters in
this specification.
@@ -671,7 +670,7 @@
implementations are possible, and implementors should release an unprefixed implementation
of any CR-level feature they can demonstrate to be correctly implemented according
to spec.
- </p
+ </p>
<p>
To establish and maintain the interoperability of CSS across implementations, the
CSS Working Group requests that non-experimental CSS renderers submit an implementation
Received on Tuesday, 24 January 2012 19:43:27 UTC