Re: [csswg-drafts] [css-multicol-2] `column-height` and nested fragmentation (#11977)

Putting things in @mstensho 's terms, I think essentially (details later), what the group wanted was something like behavior A when the column row heights are bigger than those of the fragmentainers, and behavior C when they are smaller (with something robust enough to deal with the fact that they're not all necessarily all the same height).

In my understanding, the way we were proposing to get there is effectively:
* @mstensho 's "Option A" on the first column row (first = first per fragmentainer, not first in the whole fragmented flow)
* Almost the same as @mstensho 's "Option C" on every subsequent column row, with the one difference being effectively about what an implied `align-content: normal` means: @mstensho's proposal corresponds to `stretch`, while we were going for `start`

For me, the difference between `stretch` and `start` is not that important. I can see arguments both ways, and I expect we'll eventually enable authors to set `align-content` and chose by themselves.

But I do think that treating the first row differently from subsequent ones is important: C (modulo the `stretch` question) is a better behavior in when (most) column rows are shorter than (most) fragmentainers, but we cannot do it all the time: if a row at the start of a fragmentainer is taller than the fragmentainer, pushing it to the next one won't help if the next fragmentainer is the same size, and just chopping it loses content, which is why behavior A is better when column rows are taller than fragmentainers.



-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11977#issuecomment-3530339725 using your GitHub account


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

Received on Friday, 14 November 2025 00:46:18 UTC