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

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

* `RESOLVED: have 0 sized fragments pushed to next fragmentainer if content before has overflows its fragmentainer`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Empty fragment at fragmentainer boundary<br>
&lt;fantasai> issue about including padding in scrollable overflow area -- 12 upvootes, more than pretty much any other issue I've seen, + 18 on a comment further down the line supporting it https://github.com/w3c/csswg-drafts/issues/129<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1529#issuecomment-415592931<br>
&lt;dael> fantasai: I added text to spec but realized we saida  0 size fragment stays with previous page. Doesn't seem to becase if whatever came before overflows fragmentaner.<br>
&lt;dael> fantasai: If I've got an unbreakable box that overflows and a 0 height after it moves to the next column.<br>
&lt;dael> fantasai: Wanted to check that's what we want.<br>
&lt;dael> fantasai: If anyone wants to look more<br>
&lt;dael> astearns: Makes sense to me. In your note say can be pushed. Perhaps must be pushed?<br>
&lt;dael> fantasai: Makes sense. Change from can to will<br>
&lt;dael> astearns: Okaya<br>
&lt;dael> ??: Should it still be pushed if not content after 0 height thing?<br>
&lt;dbaron> s/??/bradkemper/<br>
&lt;dael> fantasai: Yeah<br>
&lt;dael> bradk: Create a new column with nothing in it<br>
&lt;dael> fantasai: Might have something in it<br>
&lt;dael> bradk: That's useful thing?<br>
&lt;dael> fantasai: is what happens currently. If something is visible generally don't want it below fragmentainer height<br>
&lt;dael> bradk: Alright, you've convinced me<br>
&lt;Rossen_> Are we still preserving the model of minimizing the number of empty boxes due to 0 size fragments<br>
&lt;dael> astearns: Other concerns?<br>
&lt;dael> astearns: Rossen_ on IRC asks [reads]<br>
&lt;dael> astearns: I think that's restating bradk concern...<br>
&lt;dael> fantasai: We're not. Making sure no element starts below end of fragmentaner. Which is good because sometimes can't see below end of fragmentainer it gets clipped<br>
&lt;astearns> Rossen_: OK with that?<br>
&lt;fantasai> s/:/,/<br>
&lt;dael> [waiting for Rossen_ to answer in IRC]<br>
&lt;Rossen_> OK, that's fine. My question was - once an element is to be positined (margins are consumed) and is 0 size - it gets placed on the current fragment right?<br>
&lt;fantasai> see also Tab's note about how this is how Flexbox works already<br>
&lt;fantasai> If we haven't already overflowed the current fragmentainer, yes<br>
&lt;fantasai> If we've already overflowed, no, it moves to the next one<br>
&lt;Rossen_> OK, that makes more sence, thanks<br>
&lt;dael> astearns: Any other questions or concerns?<br>
&lt;dael> astearns: Objections to have 0 sized fragments pushed to next fragmentainer if content before has overflows its fragmentainer?<br>
&lt;dael> RESOLVED: have 0 sized fragments pushed to next fragmentainer if content before has overflows its fragmentainer<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-417015453 using your GitHub account

Received on Wednesday, 29 August 2018 16:24:35 UTC