Skip to content

Commit 077d15c

Browse files
fantasaifantasai
committed
[css-break] Resolve last issue. Mark other question as an issue so that we get feedback on it (hopefully).
1 parent c80f9a6 commit 077d15c

2 files changed

Lines changed: 31 additions & 32 deletions

File tree

‎css-break/Overview.html‎

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
rel=dcterms.rights>
1313
<meta content="CSS Fragmentation Module Level 3" name=dcterms.title>
1414
<meta content=text name=dcterms.type>
15-
<meta content=2014-10-28 name=dcterms.date>
15+
<meta content=2014-11-19 name=dcterms.date>
1616
<meta content="Rossen Atanassov" name=dcterms.creator>
1717
<meta content="Microsoft Corporation" name=dcterms.creator>
1818
<meta
@@ -36,7 +36,7 @@ <h1 id=css-fragmentation-module>CSS Fragmentation Module Level 3</h1>
3636
<h2 class="no-num no-toc" id=subtitle>Breaking the Web, one fragment at a
3737
time</h2>
3838

39-
<h2 class="no-num no-toc">Editor's Draft 28 October 2014</h2>
39+
<h2 class="no-num no-toc">Editor's Draft 19 November 2014</h2>
4040

4141
<dl>
4242
<dt>This version:
@@ -305,8 +305,8 @@ <h2 id=intro><span class=secno>1. </span> Introduction</h2>
305305

306306
<p> In CSS, in addition to paged media, certain layout features such as <a
307307
href="http://www.w3.org/TR/css3-regions/">regions</a> <a
308-
href="#ref-CSS3-REGIONS"
309-
rel=biblioentry>[CSS3-REGIONS]<!--{{CSS3-REGIONS}}--></a> and <a
308+
href="#ref-CSS-REGIONS-1"
309+
rel=biblioentry>[CSS-REGIONS-1]<!--{{CSS-REGIONS-1}}--></a> and <a
310310
href="http://www.w3.org/TR/css3-multicol/">multi-column layout</a> <a
311311
href="#ref-CSS3COL" rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a> create
312312
a similarly fragmented environment. The generic term for breaking content
@@ -960,10 +960,10 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
960960
the fragmentainer edge if there are no <a href="#possible-breaks">possible
961961
break points</a> on the fragmentainer.
962962

963-
<p> When paginating, if there are no possible break points below the top of
964-
the page, and not all the content fits, the UA may break anywhere in order
965-
to avoid losing content off the edge of the page. <span class=issue>Should
966-
this be generalized to fragmentainer?</span>
963+
<p> When fragmenting, if there are no possible break points below the top
964+
of the fragmentainer, and not all the content fits, the UA may break
965+
anywhere in order to avoid losing content off the edge of the
966+
fragmentainer.
967967

968968
<p class=note> Other layout models may add breakpoints to the above
969969
classes. For example, <a href="#ref-CSS3-FLEXBOX"
@@ -1004,8 +1004,8 @@ <h3 id=break-types><span class=secno>4.2. </span> Types of Breaks</h3>
10041004
<dd> A break between two <a
10051005
href="http://www.w3.org/TR/css3-regions/#regions">regions</a>. Note that
10061006
if the region boxes are on different pages, then the break is also a <a
1007-
href="#page-break"><i>page break</i></a>. <a href="#ref-CSS3-REGIONS"
1008-
rel=biblioentry>[CSS3-REGIONS]<!--{{!CSS3-REGIONS}}--></a>
1007+
href="#page-break"><i>page break</i></a>. <a href="#ref-CSS-REGIONS-1"
1008+
rel=biblioentry>[CSS-REGIONS-1]<!--{{!CSS-REGIONS-1}}--></a>
10091009
</dl>
10101010

10111011
<p class=note> A fifth type of break is the <dfn id=line-break>line
@@ -1105,10 +1105,10 @@ <h3 id=unforced-breaks><span class=secno>4.4. </span> Unforced Breaks</h3>
11051105
<p> If that still does not lead to sufficient break points, rule 3 is
11061106
dropped as well, to find still more break points.
11071107

1108-
<p class="note issue">This means that ‘<a href="#widows"><code
1108+
<p class=issue>This means that ‘<a href="#widows"><code
11091109
class=property>widows</code></a>’ and ‘<a href="#orphans"><code
11101110
class=property>orphans</code></a>’ restrictions are given priority over
1111-
the ‘<code class=css>break-*</code>’ controls.
1111+
the ‘<code class=css>break-*</code>’ controls. Is this appropriate?
11121112

11131113
<h3 id=best-breaks><span class=secno>4.5. </span> Optimizing Unforced
11141114
Breaks</h3>
@@ -1786,6 +1786,16 @@ <h3 class=no-num id=normative-references>Normative references</h3>
17861786
<dd style="display: none"><!-- keeps the doc valid if the DL is empty -->
17871787
<!---->
17881788

1789+
<dt id=ref-CSS-REGIONS-1>[CSS-REGIONS-1]
1790+
1791+
<dd>Rossen Atanassov; Alan Stearns. <a
1792+
href="http://www.w3.org/TR/2014/WD-css-regions-1-20141009/"><cite>CSS
1793+
Regions Module Level 1.</cite></a> 9 October 2014. W3C Working Draft.
1794+
(Work in progress.) URL: <a
1795+
href="http://www.w3.org/TR/2014/WD-css-regions-1-20141009/">http://www.w3.org/TR/2014/WD-css-regions-1-20141009/</a>
1796+
</dd>
1797+
<!---->
1798+
17891799
<dt id=ref-CSS21>[CSS21]
17901800

17911801
<dd>Bert Bos; et al. <a
@@ -1796,16 +1806,6 @@ <h3 class=no-num id=normative-references>Normative references</h3>
17961806
</dd>
17971807
<!---->
17981808

1799-
<dt id=ref-CSS3-REGIONS>[CSS3-REGIONS]
1800-
1801-
<dd>Rossen Atanassov; Alan Stearns. <a
1802-
href="http://www.w3.org/TR/2014/WD-css3-regions-20140218/"><cite>CSS
1803-
Regions Module Level 1.</cite></a> 18 February 2014. W3C Working Draft.
1804-
(Work in progress.) URL: <a
1805-
href="http://www.w3.org/TR/2014/WD-css3-regions-20140218/">http://www.w3.org/TR/2014/WD-css3-regions-20140218/</a>
1806-
</dd>
1807-
<!---->
1808-
18091809
<dt id=ref-CSS3-TRANSFORMS>[CSS3-TRANSFORMS]
18101810

18111811
<dd>Simon Fraser; et al. <a
@@ -1888,10 +1888,10 @@ <h3 class=no-num id=other-references>Other references</h3>
18881888
<dt id=ref-CSS3-FLEXBOX>[CSS3-FLEXBOX]
18891889

18901890
<dd>Tab Atkins Jr.; fantasai; Rossen Atanassov. <a
1891-
href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/"><cite>CSS
1892-
Flexible Box Layout Module Level 1.</cite></a> 25 March 2014. W3C Last
1893-
Call Working Draft. (Work in progress.) URL: <a
1894-
href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/">http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/</a>
1891+
href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/"><cite>CSS
1892+
Flexible Box Layout Module Level 1.</cite></a> 25 September 2014. W3C
1893+
Last Call Working Draft. (Work in progress.) URL: <a
1894+
href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/">http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/</a>
18951895
</dd>
18961896
<!---->
18971897

‎css-break/Overview.src.html‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -655,10 +655,9 @@ <h3 id="possible-breaks">
655655
</p>
656656

657657
<p>
658-
When paginating, if there are no possible break points below the top
659-
of the page, and not all the content fits, the UA may break anywhere
660-
in order to avoid losing content off the edge of the page.
661-
<span class="issue">Should this be generalized to fragmentainer?</span>
658+
When fragmenting, if there are no possible break points below the top
659+
of the fragmentainer, and not all the content fits, the UA may break anywhere
660+
in order to avoid losing content off the edge of the fragmentainer.
662661
</p>
663662

664663
<p class="note">
@@ -793,8 +792,8 @@ <h3 id="unforced-breaks">
793792
dropped as well, to find still more break points.
794793
</p>
795794

796-
<p class="note issue">This means that 'widows' and 'orphans' restrictions
797-
are given priority over the 'break-*' controls.
795+
<p class="issue">This means that 'widows' and 'orphans' restrictions
796+
are given priority over the 'break-*' controls. Is this appropriate?
798797

799798
<h3 id="best-breaks">
800799
Optimizing Unforced Breaks</h3>

0 commit comments

Comments
 (0)