- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Aug 2023 22:26:45 +0000
- To: public-css-archive@w3.org
> This case isn't relevant here, right? It applies when you're using the static position, which now would only be when you're not using a self-alignment property. So that would continue working as it currently does. [Discussed this on IRC a bit, dumping notes here for clarity] Yes, I agree it'd continue working; I just was wondering if we might want to opt this scenario into a version of the new special case, since this proposal is premised on detecting a signal from the author that they want to align this abspos thing, and for flex containers as-implemented in browsers right now, `justify-content` is the only way to align their abspos children and hence is the way that authors might send such a signal. But per IRC, it sounds like "no". The intent is that `justify-self:center` would ultimately Just Work for position:absolute things in a flex container just like it does in a grid container; and it would be subject to the proposal here, and would work by impacting how the inset properties resolve. (Whereas `justify-content` would continue to impact the static position.) -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9124#issuecomment-1666236720 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 August 2023 22:26:47 UTC