- From: Alison Maher via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Apr 2022 18:31:03 +0000
- To: public-css-archive@w3.org
@fantasai @tabatkins the latest flex fragmentation implementation in Chromium hasn't shipped yet, which is why you are seeing this behavior (although it likely will be turned on soon https://chromium-review.googlesource.com/c/chromium/src/+/3594004). With `--enable-blink-features=LayoutNGFlexFragmentation`, this is what that test case looks like in Chromium:  We do have to store some info (such as item offsets) between fragmentainers to get this to work, but we don't pass info back and forth (we only pass it in the forward direction). We will adjust offsets and the intrinsic block size of the container if things are shifted as a result of fragmentation. But we never go back to a fragmentainer that has already completed layout. To avoid circularities, we may break certain flex-specific rules as a result of fragmentation (ex. we may layout an item past the end of the container when it is end-aligned if one of the items had break that caused things to get shifted down). This matches how we are currently handling flex row fragmentation (and grid fragmentation) in Chromium. I suppose we can leave the spec as-is if you both feel strongly, but I suspect we won't plan to update the implementation in Chromium to match (unless of course we receive bugs around this). cc: @bfgeek in case you feel differently. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6855#issuecomment-1102959875 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 April 2022 18:31:05 UTC