Repository navigation
[css-multicol] Should contained out-of-flow descendants affect column balancing? #6279
Description
Out-of-flow positioned boxes usually don't affect the size of their ancestors (with the exception of any scrollbars that an OOF might cause).
However:
<p>Should there be a yellow 100px tall multicol container below, with three
columns, with one blue square in each?</p>
<div style="columns:3; background:yellow;">
<div style="position:relative;">
<div style="position:absolute; width:100px; height:300px; background:blue;"></div>
</div>
</div>
Gecko and Blink show three blue squares in a 100px tall yellow multicol container here, i.e. the OOF affects the height of the multicol container. Is this how we want things?
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
rachelandrew commentedon May 11, 2021
Safari is doing the same thing, so we do have interop in terms of browsers. So the question really is whether we are happy for multicol to behave differently to other things.
rachelandrew commentedon May 12, 2021
CodePen https://codepen.io/rachelandrew/pen/30b942f144550fa53394da7cfa4cbafd
css-meeting-bot commentedon May 12, 2021
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 specThe full IRC log of that discussion
<dael> Topic: [css-multicol] Should contained out-of-flow descendants affect column balancing?<dael> github: https://github.com//issues/6279
<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
<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
<dael> astearns: We have interop but not based on spec text?
<dael> rachelandrew: I think that's right
<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
<dael> astearns: Any opinions on the other side?
<dael> astearns: Or just generally against
<TYLin> +1 for current behavior
<dael> astearns: Prop: Add the current interop situation to the spec
<dael> astearns: Objections?
<dael> RESOLVED: Add the current interop situation to the spec
[LayoutNG] OOFs and column balancing
[LayoutNG] OOFs and column balancing
[LayoutNG] OOFs and column balancing
[LayoutNG] OOFs and column balancing
[LayoutNG] OOFs and column balancing
[LayoutNG] OOFs and column balancing
[LayoutNG] OOFs and column balancing
Bug 1721851 [wpt PR 29748] - [LayoutNG] OOFs and column balancing, a=…
Bug 1721851 [wpt PR 29748] - [LayoutNG] OOFs and column balancing, a=…