- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Sep 2021 20:21:19 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-position][css-align] How do other alignments affect the inset-modified containing block? == https://drafts.csswg.org/css-position/#abspos-insets says > If both inset properties in a given axis are auto, then, depending on the box’s self-alignment property in the relevant axis: > - for self-start alignment or its equivalent > Set its start-edge inset property to the static position, and its end-edge inset property to zero. > - for self-end alignment or its equivalent > Set its end-edge inset property to the static position, and its start-edge inset property to zero. > - for center alignment > ... What should happen for other alignments? Like, the initial [`justify-self`](https://drafts.csswg.org/css-align-3/#propdef-justify-self) is `auto`, which is typically `normal`. https://drafts.csswg.org/css-align-3/#justify-abspos > For all other absolutely-positioned boxes, `normal` behaves as `stretch`. So what's the inset-modified containing block for `stretch`? Are we supposed to use https://drafts.csswg.org/css-align-3/#abspos-sizing ? > Treat `normal` as `start` That seems to match implementations. But what if I specify `justify-self: stretch`? This is all very confusing because both css-position and css-align monkeypatch both css2 and each other. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6607 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 September 2021 20:21:21 UTC