- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Aug 2022 05:27:07 +0000
- To: public-css-archive@w3.org
> I'm in support of removing any effect of the *-content properties on positioned elements Seems like this should be doable for `align-content` at least, since AFAIK it already has no effect on positioned flex children in Blink/WebKit. I'm fine making this change in Firefox, if we've got agreement on it and ideally some spec text. It's kind of unfortunate (particularly with the current & maybe long-term asymmetry of `align-self` vs. `justify-content`), but it's where we are, I guess. RE hypothetically fixing that asymmetry and ignoring `justify-content`: I like this idea in theory (i.e. I like the idea of fully switching to only respect `align-self` / `justify-self` for aligning the staticpos of abspos flex children), but I'm a bit skeptical that it'll be web-compatible in the `justify` axis, given that: a) all browsers currently respect `justify-content` for these children (and we'd need to stop doing that) b) no browsers currently respect `justify-self` for these children (and you're proposing we start doing that) Having said that: if use counters prove it to be shippable without breaking the web, it'd be a pretty trivial change for us, implementation-wise, and I'd be happy to make that change as long as we're not the only ones to do so. :) -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7596#issuecomment-1217477264 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 August 2022 05:27:09 UTC