- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Sep 2022 01:52:21 +0000
- To: public-css-archive@w3.org
@bfgeek To me, the point is: without additional constraints, it may be true that the fragment consumes all the space, but it may not be. And not only is the actual space consumed dependent on the properties of the fragmentation context (which is fine), it also depends (at least in some cases) on the content of the fragmented box, which is not fine in the case of size containment. Making size contained elements monolithic is sufficient to solve the issue, but is more than strictly necessary. I think that creating a notion of quasi-monolithic (roughly) defined as above, and calling for size-contained elements to be that would dial down the requirements to what is strictly necessary, while keeping them sufficient. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5648#issuecomment-1240124216 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 September 2022 01:52:23 UTC