Skip to content

Commit 8bf2040

Browse files
committed
[css-break] Split out contradictory example into a note.
1 parent d724c67 commit 8bf2040

2 files changed

Lines changed: 15 additions & 9 deletions

File tree

css-break/Overview.bs

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,9 @@ Nested Fragmentation Flows</h3>
181181
<p>
182182
Breaking a <i>fragmentainer</i> <var>F</var> effectively splits the <i>fragmentainer</i>
183183
into two <i>fragmentainers</i> (<var>F<sub>1</sub></var> and <var>F<sub>2</sub></var>).
184-
The only difference is that the type of break
184+
The only difference is that,
185+
with regards to the content of <i>fragmentainer</i> <var>F</var>,
186+
the type of break
185187
between the two pieces <var>F<sub>1</sub></var> and <var>F<sub>2</sub></var>
186188
is the <a href="#break-types">type of break</a> created
187189
by the <i>fragmentation context</i> that split <var>F</var>,
@@ -192,7 +194,9 @@ Nested Fragmentation Flows</h3>
192194
For example, if a region box is broken at a page boundary,
193195
then the content of the region will be affected by a page break at that point
194196
(but not by a region break).
197+
</div>
195198

199+
<div class="note">
196200
Note that when a multi-column element breaks across pages,
197201
it generates a new row of columns on the next page for the rest of its content,
198202
so that a page break within a multi-column element

css-break/Overview.html

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -493,27 +493,29 @@ <h3 class="heading settled" data-level="2.2" id="nested-flows"><span class="secn
493493
<p>
494494
Breaking a <a data-link-type="dfn" href="#fragmentainer">fragmentainer</a> <var>F</var> effectively splits the <a data-link-type="dfn" href="#fragmentainer">fragmentainer</a>
495495
into two <a data-link-type="dfn" href="#fragmentainer">fragmentainers</a> (<var>F<sub>1</sub></var> and <var>F<sub>2</sub></var>).
496-
The only difference is that the type of break
496+
The only difference is that,
497+
with regards to the content of <a data-link-type="dfn" href="#fragmentainer">fragmentainer</a> <var>F</var>,
498+
the type of break
497499
between the two pieces <var>F<sub>1</sub></var> and <var>F<sub>2</sub></var>
498500
is the <a href="#break-types">type of break</a> created
499501
by the <a data-link-type="dfn" href="#fragmentation-context">fragmentation context</a> that split <var>F</var>,
500502
not the type of break normally created by <var>F</var>’s own <a data-link-type="dfn" href="#fragmentation-context">fragmentation context</a>.
501503
</p>
502504

503505

504-
<div class="example" id="example-e886cbbf"><a class="self-link" href="#example-e886cbbf"></a>
506+
<div class="example" id="example-336a11b1"><a class="self-link" href="#example-336a11b1"></a>
505507
For example, if a region box is broken at a page boundary,
506508
then the content of the region will be affected by a page break at that point
507509
(but not by a region break).
510+
</div>
508511

509-
510-
<p>Note that when a multi-column element breaks across pages,
512+
513+
<div class="note" role="note">
514+
Note that when a multi-column element breaks across pages,
511515
it generates a new row of columns on the next page for the rest of its content,
512516
so that a page break within a multi-column element
513-
is always both a page break and a column break.</p>
514-
515-
516-
</div>
517+
is always both a page break and a column break.
518+
</div>
517519

518520

519521
<h2 class="heading settled" data-level="3" id="breaking-controls"><span class="secno">3. </span><span class="content">

0 commit comments

Comments
 (0)