Re: [csswg-drafts] [css-multicol] Do we need column-wrap as well as column-height (#11754)

Back looking at this after an I/O induced hiatus...

So, I believe this new behavior will never occur in paged contexts, which don't have _overflow columns_, because in paged media we have this forced break. In the multicolumn model section we have:

> If the multi-column container is paginated, the height of each column is constrained by the page and the content continues in a new line of column boxes on the next page; a column box never splits across pages.

and also for spanners:

> The same effect occurs when a spanning element divides the multi-column container: the columns before the spanning element are balanced and shortened to fit their content. Content after the spanning element then flows into a new, subsequent line of column boxes.

We're already defining this as _lines_. So we wouldn't expect gaps and rules, for example, to go between lines, whereas we do expect them to go between rows.

In addition, in continuous contexts where we do have multiple rows, each row could contain multiple lines (due to spanners, as in the diagram in https://github.com/w3c/csswg-drafts/issues/11976#issuecomment-2753981259). So I *think* the wrapping you are talking about is the wrapping of lines, and not this sort of author-dictated wrapping in continuous contexts.

(I'm working on adding essentially what I've just described to the model section of the spec.)

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


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

Received on Friday, 20 June 2025 12:28:38 UTC