- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Aug 2023 20:41:21 +0000
- To: public-css-archive@w3.org
To clarify, all I was saying above was: if we were to **literally apply the suggestion here to today's web engines as-they-currently-exist**, i.e. just change them such that top/right/bottom/left `auto` would be treated as `0` when self-alignment is happening in that axis, then we would end up rendering the top half of my jsfiddles like the bottom half. (Since the bottom half of each jsfiddle is just the top half with `inset:0` added.) And that seems not-great. It sounds like you & Ian are saying that that's because in fact nobody is rendering the bottom half of my jsfiddles correctly right now, though. And if we rendered the bottom-half correctly, **then** changing to make the top half match the bottom half would be a no-op in some cases (per Ian's screenshot above) and a net improvement in following-the-alignment other cases (which is what's motivating this proposal). (Also: I'm curious about your thoughts regarding whether we need to expand this to cover `justify-content` as well, since that's what gets used in-practice to center-align the static position (i.e. auto insets) for abspos flex children?) -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9124#issuecomment-1666159951 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 20:41:23 UTC