Re: [csswg-drafts] [css-align-3][css-multicol] How is the last-baseline of a multi-col determined? (#7639)

The CSS Working Group just discussed `How is the last-baseline of a multi-col determined?`, and agreed to the following:

* `RESOLVED: (and vice-versa for the last baseline)`
* `RESOLVED: for multicolumns, use the lowest last baseline of all columns as its last baseline`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> Topic: How is the last-baseline of a multi-col determined?<br>
&lt;fremy> RESOLVED: (and vice-versa for the last baseline)<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/7639<br>
&lt;fremy> iank_: for multicolumns elements, we currently take the baseline of the first column<br>
&lt;fremy> iank_: and implementations don't look for a last baseline<br>
&lt;fremy> iank_: maybe we should?<br>
&lt;fremy> iank_: but it's still an option not to, like we do today<br>
&lt;TabAtkins> q+<br>
&lt;fremy> iank_: we can take the last baseline of the first column<br>
&lt;fremy> iank_: or of the last column<br>
&lt;fremy> iank_: or the lowest of all the columns<br>
&lt;fremy> dbaron: exporting the baseline of a multicolumn sounds scary<br>
&lt;fremy> dbaron: especially if you have balancing going on<br>
&lt;dbaron> s/the baseline/the last baseline/<br>
&lt;fremy> iank_: if you use the last column and you balance, it will often work<br>
&lt;fremy> iank_: but without balancing, you can end up somewhere random in the height<br>
&lt;Rossen_> q?<br>
&lt;fremy> fantasai: that seems the worst indeed<br>
&lt;fremy> fantasai: I think the best would be the max<br>
&lt;fremy> TabAtkins: fantasai just said what I was about to say<br>
&lt;fantasai> s/the max/the max, and second best would be the last line of the first column/<br>
&lt;fremy> iank_: the only caveat is that we probably don't want to include spanned items<br>
&lt;fremy> fantasai: why not?<br>
&lt;fremy> fantasai: if sounds like an rare case, but why not?<br>
&lt;fremy> iank_: (nodding)<br>
&lt;fremy> fantasai: I think checking all columns is better<br>
&lt;rachelandrew> +1 to checking all columns<br>
&lt;fremy> fantasai: in case you have a large image that doesn't fit at the bottom of the first column<br>
&lt;fremy> iank_: I'm fine with that<br>
&lt;fremy> iank_: we have some compat constraints for inline-block<br>
&lt;fremy> iank_: but here it's ok<br>
&lt;fremy> fantasai: proposed resolution is to use the lowest last baseline of all columns<br>
&lt;fremy> Rossen_: any objection?<br>
&lt;fremy> RESOLVED: for multicolumns, use the lowest last baseline of all columns as its last baseline<br>
&lt;TabAtkins> ScribeNick:<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 15 September 2022 19:28:53 UTC