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.

Thank you. I think this is where my confusion came from. Lines, not rows. As long as `column-height` isn't used, there'll be no change.

Here's a pagination example that does use `column-height` and `column-wrap:nowrap`, though:

```html
<!DOCTYPE html>
<style>
  @page {
    size: 20em 10em;
    margin: 0;
  }
  body {
    margin: 0;
  }
  #mc {
    columns: 2;
    width: 40%;
    column-wrap: nowrap;
    column-height: 10em;
    font: 3em;
    column-rule: solid;
    background: yellow;
  }
  #mc > div {
    counter-increment: ctr;
  }
  #mc > div::before {
    content: counter(ctr);
  }
</style>
<div id="mc">
  <div></div><div></div><div></div><div></div><div></div>
  <div></div><div></div><div></div><div></div><div></div>
  <div></div><div></div><div></div><div></div><div></div>
  <div></div><div></div><div></div><div></div><div></div>
  <div></div><div></div><div></div><div></div><div></div>
</div>
```

This currently gets rendered like this in Chrome (with the feature enabled):

![Image](https://github.com/user-attachments/assets/099a8abc-c8dd-424b-a52c-6216c5f75702)

Which is correct, I guess? We run out of columns (2), and keep overflowing in the inline direction, even if we're paginated.

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


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

Received on Monday, 23 June 2025 08:01:41 UTC