- From: Morten Stenshorne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Apr 2025 06:52:58 +0000
- To: public-css-archive@w3.org
So, figure 2? Then, what if we remove the `column-wrap:nowrap` declaration, so that it's `auto`? Then it should still behave like `nowrap` (since `column-height` is `auto`) -> still figure 2. This would be incompatible with the current implementation, which does figure 1. I now realize that I brought up the same issue a month ago here: https://github.com/w3c/csswg-drafts/issues/11754#issuecomment-2717735744 , which is where I also suggested the `auto` value, but to have a different meaning than what's in the spec currently. So I think auto should be: > If nested inside another fragmentation context and `block-size` doesn't constrain the block-size of the current fragment, or if [column-height](https://drafts.csswg.org/css-multicol-2/#propdef-column-height) is not `auto`, it behaves as the value `wrap`. Otherwise it acts as `nowrap`. Probably needs to make this easier to read, but I believe this is what we want, so that we don't introduce behavior changes in cases where both `column-wrap` and `column-height` are absent. -- GitHub Notification of comment by mstensho Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11754#issuecomment-2782204839 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 April 2025 06:52:59 UTC