- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Sep 2018 19:30:43 +0000
- To: public-css-archive@w3.org
To be a bit more explicit: Figuring out the baseline-alignment shims is a part of the track sizing algorithm, and this is run for one set of tracks at a time, either the rows or the columns. In this case, step 2 figures out row heights, and assigns block-axis margins to baseline-align between rows. (Which, due to the vertical item not participating, means that everyone gets 0-sized shims; they're not baseline-aligning.) Then step 3 happens - we treat the row as fixed-size, *but we're working on the columns*. So the baseline-shim determination is *for the columns* - inline-axis margins to align things across a column. The fact that the row is fixed has no relevance here; the cyclic check we're doing is for widths (and in this case, the column widths are both fixed at 100px, so everything's cool). Then step 4 happens - the columns are fixed, rows are un-fixed (because we're calculating them again), and so the cyclic-check is made for the rows, and once again, the vertical item still depends on an intrinsically-sized track, so it still can't baseline-align. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3046#issuecomment-420032039 using your GitHub account
Received on Monday, 10 September 2018 19:30:46 UTC