- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2023 00:25:28 +0000
- To: public-css-archive@w3.org
xiaochengh has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position-1] Automatic alignment / justification == In the [Anchor Positioning Exploration](https://fantasai.inkedblade.net/style/specs/css-anchor-exploration/) proposal, the used position area implies the [default alignment / justification](https://fantasai.inkedblade.net/style/specs/css-anchor-exploration/#area-alignment). For example, if the center track is used, then the default alignment is `anchor-center`. Now that we agreed to add `inset-area` to the spec (https://github.com/w3c/csswg-drafts/issues/9145#issuecomment-1690207503), it also seems useful to further adopt default alignment to the current spec. ## Proposal When the value of `align-self` / `justify-self` is `normal`, and the `inset-area` on the corresponding axis contains the `center` track, then `normal` behaves as `anchor-center`. ## Note The [original proposal](https://fantasai.inkedblade.net/style/specs/css-anchor-exploration/#area-alignment) also sets default alignment for the `start` and `end` tracks, but I don't think they are still needed in the context of `inset-area`, because e.g. `inset-area: start` will be resolved into `inset-something: anchor(start)`, which already automatically align the element with the start edge of the anchor; same for the `end` track. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9269 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 August 2023 00:25:30 UTC