- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Sep 2019 05:36:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `multicol`, and agreed to the following: * `RESOLVED: revert the change made in #3224, and add spec issues to define this` * `RESOLVED: republish the wd of css-multicol` <details><summary>The full IRC log of that discussion</summary> <emilio> Topic: multicol<br> <emilio> Github: https://github.com/w3c/csswg-drafts/issues/4036<br> <emilio> rachelandrew: this is an edit made in #3224 (since the last wd)<br> <emilio> rachelandrew: dbaron opened this, issue has a bunch of discussion<br> <emilio> rachelandrew: I think it was left reverting the resolution in #3224, but then we need to resolve what column-fill: auto and height: auto works<br> <emilio> rachelandrew: so we need to decide<br> <emilio> rachelandrew: I wanted to sort this so I can publish another wd, and I wouldn't like to publish something that we may revert<br> <emilio> iank_: can you describe what happens right now?<br> <emilio> rachelandrew: if we're on a continuous context we only look at column-fill: auto in ???, and there were interop issues<br> <emilio> rachelandrew: Chrome is doing the new behavior, which is actually the old one that was commented out on the spec<br> <emilio> rachelandrew: dbaron has a nice table on that issue<br> <emilio> rachelandrew: the second table<br> <emilio> rachelandrew: I think if we print from the browser the behavior should be the same<br> <emilio> dbaron: yeah, I think we shouldn't get in that situation, because we'd balance the columns separately because we're printing<br> <emilio> dbaron: I think at least the last fragment in paginated mode should behave the same as the only fragment<br> <emilio> dbaron: I suggested a fix, but florian didn't agree because it was not what print formatters do<br> <emilio> dbaron: so I suggested going in the other direction<br> <emilio> dbaron: I think mstensho was fine with this if we have a clearer definition of what each combination does<br> <emilio> dbaron: it'd take me a bit<br> <emilio> astearns: so reverting would get us to a better place to improve upon right?<br> <emilio> dbaron: I think so if WebKit are fine with changing this<br> <emilio> iank_: reverting this leaves less more stuff unspecified right?<br> <emilio> rachelandrew: yeah, that's right, but we shouldn't publish something that we might revert<br> <emilio> iank_: can we mark it at risk or such?<br> <emilio> astearns: it's more of a note "we think this is wrong but we haven't figured out the implications of changing it"<br> <emilio> iank_: that seems fine for a WD<br> <emilio> astearns: but if we know it's flat wrong it may not be useful<br> <emilio> iank_: but is it wrong for sure?<br> <emilio> dbaron: I think the inconsistency is pretty wrong<br> <emilio> iank_: mstensho didn't agree looks like<br> <emilio> dbaron: I don't think he disagreed<br> <emilio> dbaron: to be clear the thing mstensho is complaining about is that `height: auto; column-fill: auto` if we revert this change<br> <emilio> dbaron: that combination is already not-defined when you're printing<br> <emilio> dbaron: so there's an existing spec gap that needs to be filled<br> <emilio> dbaron: but I don't think it's too hard since there is existing behavior (though we may not like it)<br> <emilio> florian: I think consistency between printing and formatters is important, so it is consistency between a browser on continuous contexts and printing<br> <emilio> florian: so we should revert to find a solution that doesn't break any of both<br> <emilio> astearns: iank_ had objections?<br> <emilio> iank_: I think reverting is fine<br> <emilio> astearns: proposed resolution is reverting the change and leave issues in the draft to define this<br> <emilio> rachelandrew: yeah<br> <emilio> iank_: may be useful to link to the reverted change<br> <dbaron> It looks like what Gecko does for the auto height is just to assume one column.<br> <emilio> RESOLVED: revert the change made in #3224, and add spec issues to define this<br> <emilio> RESOLVED: republish the wd of css-multicol<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4036#issuecomment-531646703 using your GitHub account
Received on Monday, 16 September 2019 05:36:55 UTC