Re: [csswg-drafts] [css-overflow-3] Intrinsic sizing of elements with continue:discard

The CSS Working Group just discussed `overflow-3`, and agreed to the following:

* `RESOLVED: intrinsic sizing only affected by forced breaks`

<details><summary>The full IRC log of that discussion</summary>
&lt;eae> Topic: overflow-3<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/3214<br>
&lt;eae> florian: intrinsic sizing, currently the spec says that, in the block direction, is from the beginning of the content to the first forced or unforced break.<br>
&lt;eae> florian: That is problematic in that we don't know where the first unforced break is until layout<br>
&lt;eae> florian: Would suggest we change it to the first forced break. From start of content to first forced break.<br>
&lt;eae> dbaron: Two thoughts, one is that I hope the content that is after the first forced break contributors to the intrinsic size of something. Not sure what but should contribute to something.<br>
&lt;eae> florian: Only talking about the discard case now.<br>
&lt;eae> dbaron: For discard that seems reasonable, for some other cases min and max content would do different things. Min content would look at first break opportunity.<br>
&lt;fantasai> while max-content looks until first forced break<br>
&lt;eae> astearns: In cases where there is a fixed height then discard<br>
&lt;eae> florian: We should only conider forced breaks only for the purpose of intristic sizing, for other purposes the spec stays unchanged.<br>
&lt;eae> fantasai: I think this makes sense<br>
&lt;eae> RESOLVED: intrinsic sizing only affected by forced breaks<br>
&lt;fantasai> it would be problematic I think for the 2nd fragmentainer and beyond, but for the first fragmentainer it's doable and reasonable<br>
</details>


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

Received on Monday, 22 October 2018 18:41:05 UTC