- From: Morten Stenshorne via GitHub <noreply@w3.org>
- Date: Wed, 24 Sep 2025 10:41:28 +0000
- To: public-css-archive@w3.org
@alisonmaher 's previous comment is insightful, and points out the problem with the original proposal. In particular, perhaps: > 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) Furthermore, making rows monolithic may leave unused space in the outer fragmentainers. Maybe that's not so bad, but, at the same time, the original proposal seems to suggest that if the row is taller than the outer fragmentainer, it will suddenly no longer be monolithic, and instead be fragmented and occupy multiple outer fragmentainers. This seems somewhat weird. to me Can they either always be monolithic, or never be monolithic? I think we should either let rows fragment freely regardless of size (option A), or adjust them so that they never fragment (option B or C). Option B and C may cause varying row sizes, though - if that's a concern. But, my demo in my previous comment demonstrates that this is already possible (unless I misunderstand the model). -- GitHub Notification of comment by mstensho Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11977#issuecomment-3327708057 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 September 2025 10:41:29 UTC