Re: [csswg-drafts] [css-align-3][css-flexbox-1][css-grid-1] Improve container baseline finding algo #7655 #7641 (#8341)

The CSS Working Group just discussed `[css-align-3][css-flexbox-1][css-grid-1] Improve container baseline finding algo #7655 #7641`, and agreed to the following:

* `RESOLVED: first/last baseline takes from the first/last item (rather than taking highest/lowest baseline)`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> fantasai: when tab and I were drafting the fixes, we ran into a few quesitons<br>
&lt;TabAtkins> fantasai: wanted to ask WG<br>
&lt;TabAtkins> fantasai: There was some confusiong whether we resolved to take baseline from "first" item or "highest" item - discussion about highest, but resoultion said first.<br>
&lt;TabAtkins> fantasai: Second is, if we take highest, what to do in a tie?<br>
&lt;Rossen_> q?<br>
&lt;TabAtkins> Rossen_: Is there a reason we're not using first? I presume this was originally what the text says<br>
&lt;TabAtkins> Rossen_: Seems reasonable for the "first" keyword<br>
&lt;TabAtkins> fantasai: This is in a grid row or similar, not clear which is "first"<br>
&lt;TabAtkins> fantasai: first and last refers to whether you take from the first or last linebox, or row<br>
&lt;TabAtkins> fantasai: for lineboxes there's a definite baseline<br>
&lt;TabAtkins> fantasai: For rows (flex rows, multicols, grid rows) it's less clear<br>
&lt;TabAtkins> fantasai: For multicol we resolved to take the highest baseline<br>
&lt;TabAtkins> iank_: Yeah for multicol we take the highest/lowest<br>
&lt;TabAtkins> iank_: Mostly bc first/last column might not hae a baseline<br>
&lt;TabAtkins> iank_: TAbles probably have some historicla stuff<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/7641#issuecomment-1292240713<br>
&lt;TabAtkins> iank_: For flexbox and grid, suspect we want first/last, bc it's more likely to match the adjacent content<br>
&lt;TabAtkins> fantasai: In October you suggested taking the highest line<br>
&lt;TabAtkins> iank_: Yeah not sure I thought it thru at the time<br>
&lt;TabAtkins> iank_: I think it may make a little more sense to do first/last, but can go either way<br>
&lt;TabAtkins> Rossen_: It sounds like everyone but Chrome is doing first/last?<br>
&lt;TabAtkins> Rossen_: Firefox/WK do first, Chrome NG does highest (per issue)<br>
&lt;TabAtkins> iank_: Not sure if that is correct.<br>
&lt;TabAtkins> iank_: I think I'm fine with whatever makes sense to other people<br>
&lt;TabAtkins> Rossen_: So do we have strong use-cases where we *dont'* want the first/last one?<br>
&lt;iank_> https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=11394<br>
&lt;TabAtkins> dholbert: I can imagine if the first flex item was an image, second is text... but even there highest isn't necessarily better<br>
&lt;TabAtkins> fantasai: it would take from the text there<br>
&lt;TabAtkins> dholbert: Unless the image was small<br>
&lt;TabAtkins> fantasai: It'd have to be *really* small, smaller than the first line, which seems unusual<br>
&lt;TabAtkins> Rossen_: I can't think of where you'd want to choose other than first or last one<br>
&lt;iank_> https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=11395<br>
&lt;TabAtkins> iank_: I think Firefox's bheavior in this test case shows a weird behavior for last baseline<br>
&lt;TabAtkins> dholbert: I think our last-baseline support is just buggy right now<br>
&lt;TabAtkins> iank_: I think everyone currently implements taking first or last item<br>
&lt;TabAtkins> iank_: But happy to change if necessary<br>
&lt;TabAtkins> Rossen_: Okay, let's resolve on first/last, if we get a strong case to do different we can change it<br>
&lt;TabAtkins> Rossen_: For now we have proof of some compat for first/last<br>
&lt;TabAtkins> RESOLVED: first/last baseline takes from the first/last item (rather than taking highest/lowest baseline)<br>
</details>


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


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

Received on Monday, 13 March 2023 15:27:59 UTC