Re: [csswg-drafts] [css-multicol] Improve column-fill and make it backward-compatible (#3224)

The CSS Working Group just discussed `Improve column-fill and make it backward-compatible,`, and agreed to the following:

* ``RESOLVED:     1. update the spec to return to the behaviour as implemented in Blink/WebKit/Edge that `column-fill: auto` balances an unconstrained container, and does not balance a constrained container``
* `RESOLVED: include min and max as constraints`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio_> topic: Improve column-fill and make it backward-compatible,<br>
&lt;emilio_> github: https://github.com/w3c/csswg-drafts/issues/3224<br>
&lt;emilio_> rachelandrew_: turns out that a commented out sentence in the spec which Blink / WebKit and Edge implement<br>
&lt;emilio_> rachelandrew_: &lt;reads from issue><br>
&lt;emilio_> rachelandrew_: Firefox does not balance, given that text was commented out in 2012<br>
&lt;emilio_> rachelandrew_: I put together a couple examples<br>
&lt;emilio_> rachelandrew_: Proposal is to update the spec to the behavior WebKit / Blink / Edge<br>
&lt;emilio_> rachelandrew_: Another issue is to include min and max constrains<br>
&lt;emilio_> rachelandrew_: And whether we should introduce a "never-balance" mode<br>
&lt;emilio_> florian[m]: I think we almost concluded last time<br>
&lt;emilio_> florian[m]: we should generally follow the behavior of everybody but firefox, except with the nuance that if it's not min- and max- we never go into the fill mode<br>
&lt;emilio_> florian[m]: as for adding a new fill behavior, not opposed but probably level 3<br>
&lt;emilio_> *2<br>
&lt;emilio_> If we didn't include the min- thing I'd be more reluctant to follow Chrome / Edge / webKit<br>
&lt;emilio_> rachelandrew_: have looked at prince and they match FF<br>
&lt;emilio_> florian[m]: I think web compat is the dominant thing here<br>
&lt;emilio_> florian[m]: 1 and 2 solve the problem sufficiently well that you can do what you want in more cases<br>
&lt;emilio_> rachelandrew_: unless people have objections I think that'd be a good resolution<br>
&lt;emilio_> emilio_: Has FF had compat issues because of that?<br>
&lt;emilio_> florian[m]: no, but others have shipped that behavior for a long time<br>
&lt;emilio_> florian[m]: and if we put 2 together it's not a bad behavior<br>
&lt;emilio_> rachelandrew_: Without being able to do the min-size thing it does get annoying, we use server-side stuff to measure content and not get the weird columns<br>
&lt;emilio_> florian[m]: right, without the 2 part I'd prefer FF, but not otherwise<br>
&lt;emilio_> RESOLVED:     1. update the spec to return to the behaviour as implemented in Blink/WebKit/Edge that `column-fill: auto` balances an unconstrained container, and does not balance a constrained container<br>
&lt;emilio_> RESOLVED: include min and max as constraints<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3224#issuecomment-468089503 using your GitHub account

Received on Thursday, 28 February 2019 00:42:29 UTC