Re: [csswg-drafts] [css-multicol-2] `column-height` and nested fragmentation (#11977)

Option 1 should be easier to implement (no need to keep track of row progress from earlier fragments), and happens to be what we're currently doing in Blink, because I made no conscious choice when implementing it, and got this for free. But I don't think this behavior makes a lot of sense. Looks like a bug, really. Can we have option 2 instead? I also think it matters if there's a column spanner there in the inner multicol that crosses the outer column boundary.

So that:

```html
<!DOCTYPE html>
<style>
  #outer {
    columns: 2;
    column-fill: auto;
    height: 160px;
    line-height: 20px;
    orphans: 1;
    widows: 1;
    column-rule: solid;
  }
  #inner {
    columns: 2;
    column-fill: auto;
    column-height: 80px;
    column-wrap: wrap;
    row-gap: 40px;
  }
</style>
<div id="outer">
  <div id="inner">
    <div style="background:hotpink;">
      a<br>b<br>c<br>d<br>e<br>f<br>g<br>h<br>i<br>j<br>
      <div style="column-span:all;">
        muhaha!<br>
        hohoho
      </div>
      k<br>l<br>
      m<br>n<br>o<br>p<br>q<br>r<br>s<br>t<br>
    </div>
  </div>
</div>
```

renders like this:

<img width="546" height="166" alt="Image" src="https://github.com/user-attachments/assets/ac71300f-54eb-4987-96ca-faa5a21b0067" />

Or can we get option 1 to make sense, also when taking the spanner discussion in https://github.com/w3c/csswg-drafts/issues/11976 into consideration?

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


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

Received on Wednesday, 30 July 2025 10:04:34 UTC