- From: Alan Stearns <stearns@adobe.com>
- Date: Tue, 5 Nov 2013 15:20:04 -0800
- To: Simon Sapin <simon.sapin@exyr.org>, "www-style@w3.org" <www-style@w3.org>
On 11/5/13 3:14 PM, "Simon Sapin" <simon.sapin@exyr.org> wrote: >Le 05/11/2013 22:55, Alan Stearns a écrit : >> Hey all, >> >> If I have some fragmented content where there are in-flow forced breaks >> *and* breaks in float content, what happens? >> >> Given this markup and some styling indicated by the class names: >> >> <article class="multicol"> >> <p>.1.</p> >> <p class="break-before">.2.</p> >> <div class="left-float"> >> <p>.3.</p> >> <p class="break-before">.4.</p> >> </div> >> </article> >> >> >> Do I get .3..1. rendered in the first column and .4..2. rendered in the >> second? After talking to Rossen I think that's the case, as the float >> content and the in-flow content would break this way given natural >>breaks >> versus forced ones. Does it make a difference whether the float is >>before >> or after the in-flow forced break in source order, or is fragmentation >> determined only by the layout boxes? I'm assuming the source order does >> not make a difference in this case. >> >> I didn't find the answer to these questions in the fragmentation draft, >>so >> it might be good to add it in. > >Why would .3. go "back" to the first column? > >Floats have to be "below" preceding blocks, so my understanding is that >.3. would be below .2., on the second column. There is a total of three >columns. You're absolutely right - I was confusing myself with the source order question (which does make a difference). My original markup had the float before the in-flow content. In that case I think you get two columns as I describe above. Thanks, Alan
Received on Tuesday, 5 November 2013 23:21:15 UTC