Account for forced breaks, not just overflow.

Tue, 31 Jul 2012 17:56:34 -0700

author
L. David Baron <dbaron@dbaron.org>
date
Tue, 31 Jul 2012 17:56:34 -0700
changeset 6471
beffd0ad5064
parent 6470
0b57818abe66
child 6472
1743788dff9d

Account for forced breaks, not just overflow.

css3-overflow/Overview.html file | annotate | diff | comparison | revisions
css3-overflow/Overview.src.html file | annotate | diff | comparison | revisions
     1.1 --- a/css3-overflow/Overview.html	Tue Jul 31 17:42:36 2012 -0700
     1.2 +++ b/css3-overflow/Overview.html	Tue Jul 31 17:56:34 2012 -0700
     1.3 @@ -265,17 +265,18 @@
     1.4     class=css>regions</code>’, then its box is not a <a
     1.5     href="#region-box"><i>region box</i></a>.) Every <a
     1.6     href="#region-box"><i>region box</i></a> is a fragmentation container, and
     1.7 -   for each <a href="#region-box"><i>region box</i></a> box from which
     1.8 -   breakable content overflows in the block dimension, there must be another
     1.9 -   <a href="#region-box"><i>region box</i></a> created as a next sibling of
    1.10 -   the previous one. <span class=issue>Or is it as though it's a next sibling
    1.11 -   of the element? Need to figure out exactly how this interacts with other
    1.12 -   box-level fixup.</span> (Breakable content might overflow in the box
    1.13 -   dimension either because of a specified size on the region box or because
    1.14 -   the region box is within a fragmentation context in which it is being
    1.15 -   broken. In other words, a single region box is never broken across columns
    1.16 -   or pages; the pieces that are in separate columns or pages are always
    1.17 -   distinct region boxes.)
    1.18 +   for each <a href="#region-box"><i>region box</i></a> which ends with a
    1.19 +   fragmentation break, (which could happen because breakable content
    1.20 +   overflows in the block dimension or because of a forced break), there must
    1.21 +   be another <a href="#region-box"><i>region box</i></a> created as a next
    1.22 +   sibling of the previous one. <span class=issue>Or is it as though it's a
    1.23 +   next sibling of the element? Need to figure out exactly how this interacts
    1.24 +   with other box-level fixup.</span> (Breakable content might overflow in
    1.25 +   the box dimension either because of a specified size on the region box or
    1.26 +   because the region box is within a fragmentation context in which it is
    1.27 +   being broken. In other words, a single region box is never broken across
    1.28 +   columns or pages; the pieces that are in separate columns or pages are
    1.29 +   always distinct region boxes.)
    1.30  
    1.31    <p class=issue> We also want ‘<code class=css>:nth-region()</code>’
    1.32     pseudo-elements to be able to apply to the pieces of an element split
     2.1 --- a/css3-overflow/Overview.src.html	Tue Jul 31 17:42:36 2012 -0700
     2.2 +++ b/css3-overflow/Overview.src.html	Tue Jul 31 17:56:34 2012 -0700
     2.3 @@ -165,8 +165,10 @@
     2.4  		However, if an element's computed 'overflow' is not ''regions'',
     2.5  		then its box is not a <i>region box</i>.)
     2.6  		Every <i>region box</i> is a fragmentation container,
     2.7 -		and for each <i>region box</i> box from which
     2.8 -		breakable content overflows in the block dimension,
     2.9 +		and for each <i>region box</i> which ends with a fragmentation break,
    2.10 +		(which could happen
    2.11 +		because breakable content overflows in the block dimension
    2.12 +		or because of a forced break),
    2.13  		there must be another <i>region box</i> created as a next sibling
    2.14  		of the previous one.
    2.15  		<span class="issue">Or is it as though it's a next sibling of

mercurial