- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 24 Jan 2012 19:51:15 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-break
In directory hutz:/tmp/cvs-serv8556
Modified Files:
Overview.html Overview.src.html
Log Message:
Outdent headers. Rewrite intro take I.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- Overview.html 24 Jan 2012 19:43:21 -0000 1.5
+++ Overview.html 24 Jan 2012 19:51:13 -0000 1.6
@@ -84,14 +84,14 @@
<hr title="Separator for header">
</div>
- <h2 class="no-num no-toc" id=abstract>Abstract</h2>
+ <h2 class="no-num no-toc" id=abstract> Abstract</h2>
<p> This module describes the fragmentation model that partitions a flow
into pages. It builds on the Page model module and introduces and defines
the fragmentation model. It adds functionality for pagination, breaking
variable fragment size and orientation, widows and orphans.
- <h2 class="no-num no-toc" id=status>Status of this document</h2>
+ <h2 class="no-num no-toc" id=status> Status of this document</h2>
<!--begin-status-->
<p>This is a public copy of the editors' draft. It is provided for
@@ -127,46 +127,47 @@
<!--end-status-->
<!--<p>The following features are at risk: …</p>-->
- <h2 class="no-num no-toc" id=contents>Table of contents</h2>
+ <h2 class="no-num no-toc" id=contents> Table of contents</h2>
<!--begin-toc-->
<ul class=toc>
- <li><a href="#intro"><span class=secno>1. </span>Introduction</a>
+ <li><a href="#intro"><span class=secno>1. </span> Introduction</a>
<ul class=toc>
- <li><a href="#placement"><span class=secno>1.1. </span>Module
+ <li><a href="#placement"><span class=secno>1.1. </span> Module
Interactions</a>
- <li><a href="#values"><span class=secno>1.2. </span>Values</a>
+ <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="#page-breaks"><span class=secno>2. </span> Page Breaks</a>
<ul class=toc>
- <li><a href="#pg-br-before-after"><span class=secno>2.1. </span> Break
- before/after elements: ‘<code
+ <li><a href="#pg-br-before-after"><span class=secno>2.1. </span>
+ Breaking before/after/inside elements: the ‘<code
class=property>page-break-before</code>’, ‘<code
- class=property>page-break-after</code>’, ‘<code
- class=property>page-break-inside</code>’ </a>
+ class=property>page-break-after</code>’, and ‘<code
+ class=property>page-break-inside</code>’ properties </a>
- <li><a href="#using-named-pages"><span class=secno>2.2. </span>Using
- named pages: ‘<code class=property>page</code>’</a>
+ <li><a href="#using-named-pages"><span class=secno>2.2. </span> Using
+ named pages: the ‘<code class=property>page</code>’
+ property</a>
- <li><a href="#breaks-inside"><span class=secno>2.3. </span>Breaks inside
- elements: ‘<code class=property>orphans</code>’,
+ <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>
- <li><a href="#allowed-pg-brk"><span class=secno>2.4. </span>Allowed page
- breaks</a>
+ <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>2.5. </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>2.6. </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>3. </span>Conformance</a>
+ <li><a href="#conformance"><span class=secno>3. </span> Conformance</a>
<ul class=toc>
- <li><a href="#conventions"><span class=secno>3.1. </span>Document
+ <li><a href="#conventions"><span class=secno>3.1. </span> Document
Conventions</a>
<li><a href="#conformance-classes"><span class=secno>3.2.
@@ -185,7 +186,7 @@
Criteria</a>
</ul>
- <li class=no-num><a href="#acknowledgments">Acknowledgments</a>
+ <li class=no-num><a href="#acknowledgments"> Acknowledgments</a>
<li class=no-num><a href="#references">References</a>
<ul class=toc>
@@ -201,47 +202,28 @@
</ul>
<!--end-toc-->
- <h2 id=intro><span class=secno>1. </span>Introduction</h2>
+ <h2 id=intro><span class=secno>1. </span> Introduction</h2>
<p><em>This section is not normative.</em>
- <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:
-
- <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> 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> 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.
+ <p> In CSS, in addition to paged media, certain layout features such as
+ regions <a href="#CSS3-REGIONS"
+ rel=biblioentry>[CSS3-REGIONS]<!--{{CSS3-REGIONS}}--></a> and multi-column
+ layout <a href="#CSS3COL" rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a>
+ 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.
- <h3 id=placement><span class=secno>1.1. </span>Module Interactions</h3>
+ <h3 id=placement><span class=secno>1.1. </span> Module Interactions</h3>
<p> This module replaces and extends the pagination controls defined in <a
href="#CSS21" rel=biblioentry>[CSS21]<!--{{CSS21}}--></a> <a
@@ -250,7 +232,7 @@
rel=biblioentry>[CSS3PAGE]<!--{{CSS3PAGE}}--></a>.</p>
<!-- End section "Modules Interactions" -->
- <h3 id=values><span class=secno>1.2. </span>Values</h3>
+ <h3 id=values><span class=secno>1.2. </span> Values</h3>
<p> This specification follows the <a
href="http://www.w3.org/TR/CSS21/about.html#property-defs"> CSS property
@@ -269,7 +251,7 @@
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=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 may or should break pages, and on
@@ -284,13 +266,14 @@
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> Break before/after
- elements: ‘<a href="#page-break-before"><code
+ <h3 id=pg-br-before-after><span class=secno>2.1. </span> Breaking
+ before/after/inside elements: the ‘<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
+ class=property>page-break-after</code></a>’, and ‘<a
href="#page-break-inside"><code
- class=property>page-break-inside</code></a>’</h3>
+ class=property>page-break-inside</code></a>’ properties</h3>
<table class=propdef summary="property definition">
<tbody>
@@ -473,8 +456,9 @@
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:
- ‘<a href="#page"><code class=property>page</code></a>’</h3>
+ <h3 id=using-named-pages><span class=secno>2.2. </span> Using named pages:
+ the ‘<a href="#page"><code class=property>page</code></a>’
+ property</h3>
<table class=propdef summary="property definition">
<tbody>
@@ -587,7 +571,7 @@
</div></pre>
</div>
- <h3 id=breaks-inside><span class=secno>2.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>
@@ -697,7 +681,7 @@
href="#orphans"><code class=property>orphans</code></a>’, the rule
simply becomes that all lines in the block must be kept together.
- <h3 id=allowed-pg-brk><span class=secno>2.4. </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 may occur at the following places:
@@ -762,7 +746,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>2.5. </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 ‘<a href="#page-break-before"><code
@@ -792,7 +776,7 @@
the used values of any adjoining ‘<code
class=property>margin-bottom</code>’ 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>2.6. </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
@@ -851,9 +835,9 @@
</div>
<!-- End section "Page Breaks" -->
- <h2 id=conformance><span class=secno>3. </span>Conformance</h2>
+ <h2 id=conformance><span class=secno>3. </span> Conformance</h2>
- <h3 id=conventions><span class=secno>3.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”,
@@ -1021,7 +1005,7 @@
<p> The specification will remain Candidate Recommendation for at least six
months.
- <h2 class=no-num id=acknowledgments>Acknowledgments</h2>
+ <h2 class=no-num id=acknowledgments> Acknowledgments</h2>
<p> The editors would like to extend special thanks to Michael Day, and the
former <a href="#CSS3PAGE"
@@ -1068,6 +1052,26 @@
<dt style="display: none"><!-- keeps the doc valid if the DL is empty -->
<!---->
+ <dt id=CSS3-REGIONS>[CSS3-REGIONS]
+
+ <dd>Vincent Hardy; Alex Mogilevsky. <a
+ href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/"><cite>CSS
+ Regions Module Level 3.</cite></a> 29 November 2011. W3C Working Draft.
+ (Work in progress.) URL: <a
+ href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/">http://www.w3.org/TR/2011/WD-css3-regions-20111129/</a>
+ </dd>
+ <!---->
+
+ <dt id=CSS3COL>[CSS3COL]
+
+ <dd>Håkon Wium Lie. <a
+ href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412"><cite>CSS
+ Multi-column Layout Module.</cite></a> 12 April 2011. W3C Candidate
+ Recommendation. (Work in progress.) URL: <a
+ href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412">http://www.w3.org/TR/2011/CR-css3-multicol-20110412</a>
+ </dd>
+ <!---->
+
<dt id=CSS3COLOR>[CSS3COLOR]
<dd>Tantek Çelik; Chris Lilley; L. David Baron. <a
@@ -1109,6 +1113,9 @@
<li>page-break-inside, <a href="#page-break-inside"
title=page-break-inside><strong>2.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>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-break/Overview.src.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- Overview.src.html 24 Jan 2012 19:43:21 -0000 1.6
+++ Overview.src.html 24 Jan 2012 19:51:13 -0000 1.7
@@ -39,7 +39,9 @@
<hr title="Separator for header">
</div>
- <h2 class="no-num no-toc" id="abstract">Abstract</h2>
+<h2 class="no-num no-toc" id="abstract">
+Abstract</h2>
+
<p>
This module describes the fragmentation model that partitions a flow into pages.
It builds on the Page model module and introduces and defines the fragmentation
@@ -47,46 +49,41 @@
orientation, widows and orphans.
</p>
- <h2 class="no-num no-toc" id="status">Status of this document</h2>
+<h2 class="no-num no-toc" id="status">
+Status of this document</h2>
<!--status-->
<!--<p>The following features are at risk: …</p>-->
- <h2 class="no-num no-toc" id="contents">Table of contents</h2>
+<h2 class="no-num no-toc" id="contents">
+Table of contents</h2>
<!--toc-->
- <h2 id="intro">Introduction</h2>
+<h2 id="intro">
+Introduction</h2>
+
<p><em>This section is not normative.</em></p>
<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>
- <ul>
- <li><a href="#page-breaks">page breaks</a> are created and avoided;</li>
- <li>the page properties such as size, orientation, margins, border, and padding are specified;</li>
- <li>headers and footers are established within the page margins;</li>
- <li>content such as page counters are placed in the headers and footers; and</li>
- <li>orphans and widows can be controlled.</li>
- </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.
+ 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>pagination</dfn>.
</p>
<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>
- <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.
+ In CSS, in addition to paged media, certain layout features such as
+ regions [[CSS3-REGIONS]] and multi-column layout [[CSS3COL]]
+ 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.
</p>
- <h3 id="placement">Module Interactions</h3>
+<h3 id="placement">
+Module Interactions</h3>
+
<p>
This module replaces and extends the pagination controls defined in
[[CSS21]] <a href="http://www.w3.org/TR/CSS21/page.html#page-breaks">section 13.3</a>
@@ -94,7 +91,9 @@
</p>
<!-- End section "Modules Interactions" -->
- <h3 id="values">Values</h3>
+<h3 id="values">
+Values</h3>
+
<p>
This specification follows the <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">
CSS property definition conventions</a> from [[!CSS21]]. Value types not defined
@@ -109,7 +108,8 @@
repeated explicitly.
</p>
- <h2 id="page-breaks">Page Breaks</h2>
+<h2 id="page-breaks">
+Page Breaks</h2>
<p>
The following sections explain page breaking in CSS3 paged media. Five properties
@@ -126,9 +126,8 @@
blank page if one exists, and onto the top of the subsequent page.
</p>
- <h3 id="pg-br-before-after">
- Break before/after elements: 'page-break-before',
- 'page-break-after', 'page-break-inside'
+<h3 id="pg-br-before-after">
+Breaking before/after/inside elements: the 'page-break-before', 'page-break-after', and 'page-break-inside' properties
</h3>
<table class="propdef" summary="property definition">
@@ -258,7 +257,9 @@
flow of the root element. User agents may also apply these properties to other boxes.
</p>
- <h3 id="using-named-pages">Using named pages: 'page'</h3>
+<h3 id="using-named-pages">
+Using named pages: the 'page' property</h3>
+
<table class="propdef" summary="property definition">
<tr>
<th>Name:
@@ -348,7 +349,9 @@
</div></pre>
</div>
- <h3 id="breaks-inside">Breaks inside elements: 'orphans', 'widows'</h3>
+<h3 id="breaks-inside">
+Breaks inside elements: 'orphans', 'widows'</h3>
+
<table class="propdef" summary="property definition">
<tr>
<th>Name:
@@ -436,7 +439,8 @@
simply becomes that all lines in the block must be kept together.
</p>
- <h3 id="allowed-pg-brk">Allowed page breaks</h3>
+<h3 id="allowed-pg-brk">
+Allowed page breaks</h3>
<p>In the normal flow, page breaks may occur at the following places:</p>
@@ -493,7 +497,9 @@
to find still more break points.
</p>
- <h3 id="forced-pg-brk">Forced page breaks</h3>
+<h3 id="forced-pg-brk">
+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 'page-break-before' properties of all the elements
@@ -518,7 +524,8 @@
of any adjoining 'margin-bottom' are set to zero.
</p>
- <h3 id="best-pg-brk">"Best" page breaks</h3>
+<h3 id="best-pg-brk">
+"Best" page breaks</h3>
<p>
CSS3 does <em>not</em> define which of a set of allowed page breaks must
@@ -577,8 +584,11 @@
<!-- End section "Page Breaks" -->
- <h2 id="conformance">Conformance</h2>
- <h3 id="conventions">Document Conventions</h3>
+<h2 id="conformance">
+Conformance</h2>
+
+<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”,
@@ -638,8 +648,10 @@
individual grammars of each feature in this module, and meet all other conformance
requirements of style sheets as described in this module.
</p>
- <h3 id="partial">
- Partial Implementations</h3>
+
+<h3 id="partial">
+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 invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">
@@ -650,8 +662,10 @@
if any value is considered invalid (as unsupported values must be), CSS requires
that the entire declaration be ignored.
</p>
- <h3 id="experimental">
- Experimental Implementations</h3>
+
+<h3 id="experimental">
+Experimental Implementations</h3>
+
<p>
To avoid clashes with future CSS features, the CSS2.1 specification reserves a <a
href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed syntax</a>
@@ -663,8 +677,10 @@
features, including those in W3C Working Drafts. This avoids incompatibilities with
future changes in the draft.
</p>
- <h3 id="testing">
- Non-Experimental Implementations</h3>
+
+<h3 id="testing">
+Non-Experimental Implementations</h3>
+
<p>
Once a specification reaches the Candidate Recommendation stage, non-experimental
implementations are possible, and implementors should release an unprefixed implementation
@@ -684,8 +700,10 @@
http://www.w3.org/Style/CSS/Test/</a>. Questions should be directed to the <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">
public-css-testsuite@w3.org</a> mailing list.
</p>
- <h3 id="cr-exit-criteria">
- CR Exit Criteria</h3>
+
+<h3 id="cr-exit-criteria">
+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 feature. Each feature
@@ -727,7 +745,10 @@
<p>
The specification will remain Candidate Recommendation for at least six months.
</p>
- <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
+
+<h2 class="no-num" id="acknowledgments">
+Acknowledgments</h2>
+
<p>
The editors would like to extend special thanks to
Michael Day,
Received on Tuesday, 24 January 2012 19:51:19 UTC