- From: Alison Maher via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Feb 2024 20:43:57 +0000
- To: public-css-archive@w3.org
I was thinking about this one some more, and I think the point from @bfgeek in the minutes is correct in that we would need to run layout to get the number of forced breaks needed. One example where this would be necessary is with relation to flexbox fragmentation. According to the [spec](https://drafts.csswg.org/css-flexbox-1/#pagination), "In a row flex container, the [break-before](https://drafts.csswg.org/css-break-3/#propdef-break-before) and [break-after](https://drafts.csswg.org/css-break-3/#propdef-break-after) values on flex items are propagated to the flex line." The main problem this poses is that there may be more than one forced break in the same line, so naively counting the number of forced breaks would be incorrect, since two forced breaks in the same line will only produce one true forced break before or after the current flex line. Unless we run layout, we will not know which items are placed in which lines, and thus, where the forced breaks will apply to (and which will be ignored due to an earlier forced break in the same line). Flex lines are also not a part of the DOM, so we do some "magic" at layout time to apply these various breaks according to where the items ended up, meaning that knowing the exact number of columns created due to forced breaks in the case of flex fragmentation is impossible before layout. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9103#issuecomment-1942457476 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 February 2024 20:44:00 UTC