Re: [csswg-drafts] [css-grid-1] Spec doesn't seem to discuss baseline-alignment + auto-margins. (#5923)

Hi, sorry for the late reply. I'm not sure I understand what's the final proposal for this issue, since there are a lot of changes in the spec and not all of them are related to auto-margin alignment. In the last comment from @tabatkins it was mentioned:

>  that auto margins only disable baseline content-alignment if they conflict with its baseline preference, identically to how self-alignment was already specified to work.

In the last draft ([16ed028](https://github.com/w3c/csswg-drafts/commit/16ed028af7c0d0a59a6b723ac15f5c817bcd6353)) it's stated clearly that the use of auto-margins in on axis disables the the self-alignment properties in such axis. Hence, it's clear that such item can't participate in baseline alignment, since it's align-self/justify-self values must be ignored. I think it's a bit confusing or redundant  that in [c78e58b](https://github.com/w3c/csswg-drafts/commit/c78e58b5ccd893de6811d7b083f57809c102a102) we use auto-margins as a limit for the grid item's participation in baseline (the root cause is that aligng-self/justify-self are ignored) and even there seems to be scenarios (if I've understood it correctly) where even with auto-margins the grid item may participate in baseline alignment (it's impossible since align-self/justify-seld must be ignored).

I've always assumed that the use of auto-margins in one axis would imply ignoring at all the value of the self-alignment properties operating on such axis. In the last published spec this was specified as:

https://www.w3.org/TR/css-grid-1/#auto-margins
> auto margins absorb positive free space prior to alignment via the box alignment properties. 

That's what motivated the initial implementation of the Alignment logic in both, Chrome and Safari. 

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


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

Received on Wednesday, 23 June 2021 09:47:22 UTC