Re: [csswg-drafts] [css-break-3] Should broken boxes always be extended to fill the gap? (#12801)

> I think what you're saying is that if we're breaking between rows, then we should actually break the (visual) box of a rowspanned cell at that point, too (if it's breakable at that point). This makes sense to me. Probably the same should apply for Grid. I don't think we're at the point where we can require this behavior, but we can suggest it.

Yes, pretty much. Though I think "breaking the (visual) box" of something is not yet a concept that exists in the spec.
[5.3.](https://www.w3.org/TR/css-break-3/#box-splitting) says that any break causes a box to grow taller, to fill the rest of its fragmentainer. So just forcing a regular break into rowspanned cells would still result in the "Current" case from my drawing above. The new type of break inserted here would need to not stretch the box out to fill the rest of the fragmentainer.

Also, if [`box-decoration-break`](https://www.w3.org/TR/css-break-3/#propdef-box-decoration-break) is set to [`clone`](https://www.w3.org/TR/css-break-3/#valdef-box-decoration-break-clone), the break would need to be inserted above the end of the row, to leave space for the bottom padding and margins and such.

I've written up some spec text that I hope does a good job at defining the behavior I had in mind with this: https://github.com/w3c/csswg-drafts/pull/12805

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


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

Received on Monday, 15 September 2025 22:46:24 UTC