- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Oct 2018 03:04:54 +0000
- To: public-css-archive@w3.org
@mstensho aha, that explains a lot of the confusion. I don't know the history of that sneaky change, but setting that aside, I think what we should spec is: * always balance before spanners. * when column-fill is auto, only fill columns other than the first (after spanners) if there is a forced break or if constrained by the used value of the height * the min content intrinsic size in the block direction is the same for `column-fill:auto` and `column-fill:balance` * The max content intrinsic size in the block direction for `column-fill:auto` is the height you get when (after any spanners and their preceding balanced content) if you only wrap to the next column at forced breaks. That seems to be the more useful behavior to me. Now, that does not match what Chrome/Safari/Edge implement and what the old CR say, but it does (at least superficially, I have not looked too close) what Firefox does and what the new ED suggests (even though it's not very specific). I am not 100% sure what that implies in terms of web compat, but I'd like to be optimistic and hope that having both behaviors means we're not too constrained. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3064#issuecomment-430859622 using your GitHub account
Received on Thursday, 18 October 2018 03:04:55 UTC