Re: [csswg-drafts] [css-break] Empty fragment at fragmentainer boundary

The Working Group just discussed `Empty fragment at fragmentainer boundary`, and agreed to the following:

* `RESOLVED: Specify 0 size elements are positioned as early as possible in the fragmentation flow`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Empty fragment at fragmentainer boundary<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1529<br>
&lt;dael> fantasai: About an empty fragment at a fragmentainer boundry.  If you have a 0 height block or 0 width inline etc and the previous item that fi there filled the whole line does the 0 size element stay on the page?<br>
&lt;dael> fantasai: Specs don't say anything now about where required to break so UA can be intellengent.<br>
&lt;dael> fantasai: For 0 size might make sense to spec explicitly<br>
&lt;dael> fantasai: Question is do we want to spec that for fragmentation in general or just for flexbox?<br>
&lt;dael> fantasai: flexbox is only place w e define that percisely right now.<br>
&lt;dael> Rossen: I believe we discussedin the past. Don't remember if resolved.<br>
&lt;fantasai> because flexbox requires consistency more than quality-of-implementation, so its breaking rules are defined<br>
&lt;dael> Rossen: As far as I recall reason is the empty elements are exausted opportunitically as much as possible. If there are empty boxes at the end of fragment we assume they fit. Done so you can reduce subsequent fragments.<br>
&lt;dael> Rossen: That makes sense<br>
&lt;dael> Rossen: Other side is such elements or boxes are used for positioning or to create containing blocks or abspos items that go in and out for UI<br>
&lt;dael> Rossen: For those cases harder to argue it's better that such items are consumed asap or pushed. Again, counter is there are avoid break-inside  and break-after properties where you can use such and control correctly<br>
&lt;dael> Rossen: In both cases makes snese to position and consume empty boxes a s early aspossible on frag where they are encountered rather then pushing<br>
&lt;dael> Rossen: That's how I remember previous<br>
&lt;dael> Rossen: Curious if there are other arguments or if we can resolve on that and spec it so we don't forget again<br>
&lt;bradk> +1<br>
&lt;dael> Rossen: Obj to Spec 0 size elements are positioned as early as possible in the fragmentation flow?<br>
&lt;dael> RESOLVED: Specify 0 size elements are positioned as early as possible in the fragmentation flow<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1529#issuecomment-415098496 using your GitHub account

Received on Wednesday, 22 August 2018 16:42:16 UTC