- From: Rachel Andrew via GitHub <noreply@w3.org>
- Date: Tue, 29 Jul 2025 15:00:13 +0000
- To: public-css-archive@w3.org
I think all of the above are true, and adding to the agenda for resolutions for two things. Firstly, to make it clear that spanners don't wrap with the columns and still only span across the container in the line direction. I'm suggesting the following amendment to the definition of `all` [here](https://www.w3.org/TR/css-multicol-2/#column-span). > The element forces a column break and is taken out of flow to span across all columns of the current multicol row in the same block formatting context. Secondly, to deal with the situation where a spanner is too tall (large in the block direction) for the defined `column-height`. There are three options as discussed in [previous comments](https://github.com/w3c/csswg-drafts/issues/11976#issuecomment-2995928881). 1. To not span at all in that situation (Not ideal as we'd need to do the layout then decide to bail). 2. To push the item to the next row, which would work for the (probably most common) scenario where we have a bunch of content then a spanner, and there's just not enough room for the spanner + the already laid out content. It would _not_ work in situations where the spanner is taller than the `column-height`. 3. To just stretch the row it appears in to make space. I'm not keen on 3 as a default as I think that would cause issues with things like carousel type layouts, or where you want the columns to be 100vh. I think that a combination of 2 and 3 probably makes sense. So do 2, if the spanner will fit as the first thing in a new row, and do 3 as a fallback for scenarios where we can't do anything better. Does this outline of the needed resolutions make sense @mstensho? -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11976#issuecomment-3132941885 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 July 2025 15:00:14 UTC