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

When an inner multicol container breaks, it generates a new row. New row means wrapping, is what I'm thinking.

Let's do printing instead. Nested multicol is bad for the brain.

```html
<!DOCTYPE html>
<style>
  @page {
    size: 500px 240px;
    margin: 20px;
  }
  body {
    line-height: 50px;
    orphans: 1;
    widows: 1;
    margin: 0;
  }
</style>
<div style="height:100px;"></div>
<div style="columns:2; column-fill:auto; height:300px; background:yellow;">
  A<br>B<br>C<br>D<br>E<br>F<br>G<br>H<br>I<br>J<br>K<br>
</div>
```

![Image](https://github.com/user-attachments/assets/4c4dc3de-0b43-4841-83a9-9b91fd313bdb)

A new row of columns is started on the second page. If we hadn't done that, and instead let columns be as tall as they want, and cross page boundaries, all in a single row, it would have looked like this:

![Image](https://github.com/user-attachments/assets/6222d5f9-9e0a-4c36-8345-bed1b8cd2aa3)

I.e. one would have to read the left column on all pages first, then turn back to page one and read the second column on all pages.

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


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

Received on Wednesday, 9 April 2025 19:13:07 UTC