Re: [csswg-drafts] [css-multicol] Should contained out-of-flow descendants affect column balancing? (#6279)

The CSS Working Group just discussed `[css-multicol] Should contained out-of-flow descendants affect column balancing?`, and agreed to the following:

* `RESOLVED: Add the current interop situation to the spec`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-multicol] Should contained out-of-flow descendants affect column balancing?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6279<br>
&lt;dael> rachelandrew: This is another one about out of flow elements. Out of flow position box doesn't normally effect ancestor size. It is happening in multicol<br>
&lt;dael> rachelandrew: We have interop,e veryone does same thing. It is different to have things behave with out of flow. Are we happy to have multicol behave different or do we want to change that<br>
&lt;dael> astearns: We have interop but not based on spec text?<br>
&lt;dael> rachelandrew: I think that's right<br>
&lt;dael> fantasai: I think we do have a use case that people use multicol to emulate pages. That would want us to do same as paginated which is generate more pages and take up space. given we have interop and one reason to do it my suggestion would be to put what they're doing in spec<br>
&lt;dael> astearns: Any opinions on the other side?<br>
&lt;dael> astearns: Or just generally against<br>
&lt;TYLin> +1 for current behavior<br>
&lt;dael> astearns: Prop: Add the current interop situation to the spec<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> RESOLVED: Add the current interop situation to the spec<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 May 2021 16:17:19 UTC