Skip to content

Commit 2f7913a

Browse files
committed
[css-page-floats] small language fixes, add definition of not overlapping
1 parent 02fe3bd commit 2f7913a

1 file changed

Lines changed: 23 additions & 15 deletions

File tree

css-page-floats/Overview.bs

Lines changed: 23 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -73,9 +73,11 @@ Terminology</h2>
7373
<dt><dfn>Float reference</dfn>
7474
<dd>
7575
The entity to which the float is aligned.
76+
<dt><dfn>Not overlapping</dfn></dt>
77+
Two elements are not overlapping if the margin box of one element is not
78+
overlapping the margin box of the other element.
7679
</dl>
7780

78-
7981
<h2 id="floating">
8082
Floating to the inline-start/inline-end and block-start/block-end</h2>
8183

@@ -794,16 +796,16 @@ img {
794796

795797
<h2 id="page-float-placement">Page float placement</h2>
796798

797-
The order of page float placement is determined by the following rules:
799+
The order of page floats placement is determined by the following rules:
798800

799801
<ol>
800802
<li>
801-
All page floats with 'float-reference' set to `page` are placed, in the
802-
order they appear in the DOM, before those with 'float-reference' set to
803-
`region` and `column`.
803+
All page floats with 'float-reference' set to `page` are placed, in
804+
document order, before those with 'float-reference' set to `region` and
805+
`column`.
804806
<li>
805807
Thereafter, page floats with 'float-reference' set to `column` and `region`
806-
are placed in the order they appear in the DOM.
808+
are placed in document order.
807809
</li>
808810
</ol>
809811

@@ -860,15 +862,15 @@ Float references can grow up to the their `max-height` and `max-width` or their
860862

861863
Page floats are stacked within a given <a>float reference</a> in the order of their
862864
placement and in the direction of the inline- and flow-directions of the
863-
<a>fragmentation context</a> without overlapping with other page floats with the same
864-
<a>float reference</a> and by keeping a distance N between the page float's
865-
margin edge and the padding edge of the <a>float reference</a> as well as between
866-
the page float's margin edge and the margin edge of the last previously placed page
867-
float with the same <a>float reference</a> and the same 'float' value, where N is
868-
the 'float-offset' value of the page float. For the placement it is assumed that
869-
the page floats in the block directions fill the entire line size of the <a>float
870-
reference</a> and page floats in the inline direction fill the entire block size
871-
of the <a>float reference</a>.
865+
<a>fragmentation context</a> while <a>not overlapping</a> with any other page
866+
floats with the same <a>float reference</a> and by keeping a distance N between
867+
the page float's margin edge and the padding edge of the <a>float reference</a>
868+
as well as between the page float's margin edge and the margin edge of the last
869+
previously placed page float with the same <a>float reference</a> and the same
870+
'float' value, where N is the 'float-offset' value of the page float. For the
871+
placement it is assumed that the page floats in the block directions fill the
872+
entire line size of the <a>float reference</a> and page floats in the inline
873+
direction fill the entire block size of the <a>float reference</a>.
872874

873875
If the page float has a defined 'clear'-value, then the <a>float reference</a> in
874876
which the page float is placed is closed for all subsequent page floats that
@@ -1089,6 +1091,12 @@ p { float-reference: page; float: top; float-defer: last }
10891091
:
10901092

10911093
<ol>
1094+
<li>
1095+
Add term definition for 'not overlapping'.
1096+
</li>
1097+
<li>
1098+
Use term "document order" instead of "order ... appear in the DOM".
1099+
</li>
10921100
<li>
10931101
Make the order of page float placement determined both by DOM and how high
10941102
in the DOM the page float reference is.

0 commit comments

Comments
 (0)