- From: Daniel Holbert via GitHub <noreply@w3.org>
- Date: Tue, 03 Feb 2026 00:01:56 +0000
- To: public-css-archive@w3.org
> The spec simply says that 'page' applies to boxes that create class A break points. In my mind that's pretty much aligned with where 'break-before' and 'break-after' apply, albeit with some exceptions, perhaps. > > For column flex in particular - https://www.w3.org/TR/css-flexbox-1/#pagination: "In a column flex container, Class A break opportunities occur between sibling flex items". Thanks - that does make [`page-name-flex-001-print.html`](https://searchfox.org/firefox-main/rev/33fd6bd39c625067a29f153adce6a4646e45750f/testing/web-platform/tests/css/css-page/page-name-flex-001-print.html) invalid, then. (Historical note, that was added in https://bugzilla.mozilla.org/show_bug.cgi?id=1786399 and I believe at that point we were going off of https://www.w3.org/TR/css-break-3/#btw-blocks as defining the complete list of things that can create class A break points -- we didn't notice that the flexbox spec added another case.) > Not sure about row flex containers. 'break-before' and 'break-after' properties are propagated to the flex line. One could imagine the same to happen for 'page', but then again maybe not so useful, since there may be multiple flex items specifying different page names for the same line. Yeah, not sure about those either; it's less obvious how the propagation (of page-names from item to line) would work there. -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9513#issuecomment-3837917768 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 February 2026 00:01:57 UTC