Re: [csswg-drafts] [css-grid] Unintentional change to grid container baseline? (#3645)

I think we should definitely use items in other tracks if the first track is empty. I don't feel strongly about exactly how a baseline is derived from that item though. Using its natural baseline, if it has one, or synthesizing one if it doesn't, make the most sense to me. I think if we remove the _"whose area intersects the first (last) row"_ condition from Step 2 then we'd get that behavior. A slightly more advanced scheme would be to remove that condition from Step 1 too.

Using the track itself makes no sense to me since baseline alignment is a content-based alignment scheme and the grid itself is not content (and to be clear: by "the grid" I mean the abstract concept outlined with a dashed border in this [figure](https://drafts.csswg.org/css-grid/#example-ff8d888d), not the grid container box). I don't see how that would be useful anyway when that track is empty.  If that track is intrinsically sized it'd be zero, otherwise it's likely a definite size so alignment to that position can likely be achieved through other means (relative position or margin or whatever on the grid container).

It seems to me that if the author intentionally wants to align the grid lines to the baseline it should be a separate concept, perhaps as a new value for [alignment-baseline](https://www.w3.org/TR/css-inline-3/#alignment-baseline-property).

-- 
GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3645#issuecomment-463804957 using your GitHub account

Received on Thursday, 14 February 2019 21:29:25 UTC