- From: Alison Maher via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 07:26:20 +0000
- To: public-css-archive@w3.org
That's a good point. Based on the discussion in https://github.com/w3c/csswg-drafts/issues/11976, I think we resolved that spanners can take up space in more than one row, which I suppose means that the spanner could still fragment and consume space in the row that starts in the next fragmentainer (assuming it isn't itself monolithic). But where pushing a monolithic row to the next fragmentainer causes extra space at the end of the initial fragmentainer that a spanner could take up if it started in the first row (or was placed right after the first row) - will it take up that space or not (I'd assume it would, but that could be quite strange) So maybe you would need to stretch the row to fill the whole fragmentainer. And I suppose you could tell when this is needed by comparing the row size to the remaining fragmentainer space that you have, and stretch to fill the space before consuming for inner content -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11977#issuecomment-3209340216 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 07:26:21 UTC