- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 20:57:00 +0000
- To: public-css-archive@w3.org
> The align-self and justify-self properties initialize to auto, which for absolutely-positioned elements does not reference the container`. https://www.w3.org/TR/css-align-3/#valdef-justify-self-auto This isn't clear from the spec to me - can you quote the place where this is mentioned? > We might have a compat problem here that we need to address for flexbox particularly, but the ideal behavior here is that align-items has no effect on abspos descendants. Hmmm - we have a larger issue here then. Currently align-items for both grid and flex (interoperably across all engines) affect the static position. I believed that we were going to keep the `align-items`, and `justify-items` behaviour for grid. > Looking more closely here, it appears that the current behavior of browsers is just to apply the "inheritance" of *-self for the purpose of calculating the static position (of abspos flexbox children). I can't get any browser to pay attention to *-self properties for the normal alignment of the abspos, so I presume that's not implemented at all yet and we can rely on the current spec explicitly not looking up at *-items when determining its behavior. (See https://jsfiddle.net/dyp9uwea/.) Right that's what I was looking at implementing - as well as the staticpos rectangle alignment. I suspect we *aren't* compat constrained in the `align-self` / `justify-self` properties (but *are* compat constrainted with the `align-items` / `justify-items` ). > (and relatedly: in practice, does this only change behavior for abspos flex children?) Abspos flex children in a column flexbox. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1226327642 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 August 2022 20:57:01 UTC