Re: [csswg-drafts] [css-multicol-2] `column-wrap`, `column-height` and column balancing (#11976)

That's a nice diagram! Thank you.

Thinking of block direction wrapping as similar to paged multicol seems fine, though we might of course have multiple rows per page as well. But I don't see that as another nesting level. We're simply breaking as before, but placing the remaining stuff below rather than beside. Probably something we should discuss elsewhere if needed, in any case.

Your suggested definition of `column-span:all` also makes sense. But how about *current multicol row* rather than *nearest multicol row*?

What if the spanner overflows the row (in the block direction)?

E.g.:
```html
<!DOCTYPE html>
<div style="columns:3; column-fill:auto; column-height:100px; column-wrap:wrap; line-height:20px; background:yellow;">
  <div style="background:cyan;">
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    <div style="column-span:all; height:100px; border:solid;">SQUIRREL!</div>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
    line<br>line<br>line<br>line<br>line<br>
  </div>
</div>
```

Without the spanner, it would look like this. Row gaps shown with dashed borders:

![Image](https://github.com/user-attachments/assets/268addfa-c8ff-47b4-bac0-4e3bd296ad60)

Now with the spanner in the works, still with dashed row gaps shown pretending that all rows become 100px tall (this is with the current implementation, and, based on this discussion, not exactly what we want, but it should still illustrate the problem):

![Image](https://github.com/user-attachments/assets/b52be271-5bd0-4598-b42a-6c66541b2512)

Looks like `column-span: <integer>` isn't fully defined at all, so I don't know if we need to worry about it. Maybe it's infeasible (except with page floats, if we ever want to go there)? Maybe even more so after introducing column wrapping? 😉 

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


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

Received on Wednesday, 26 March 2025 12:54:52 UTC