- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2023 00:43:31 +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] Do we need area-list fallback position syntax? ==
(This is a sub-topic from the [feature comparison](https://github.com/w3c/csswg-drafts/issues/9117) issue)
The [grid-based proposal](https://fantasai.inkedblade.net/style/specs/css-anchor-exploration/#fallback) has a list based fallback syntax, for example:
```css
.target {
position-area: top / all, bottom / all, left / all, right / all;
}
```
The current spec doesn't have anything similar, but will have auto position fallback that allows automatically generating a list of fallback styles from a base style. See https://github.com/w3c/csswg-drafts/issues/9196#issuecomment-1690225805
I'm opening this issue to gather opinions on whether the auto position fallback syntax is enough for simple cases, or do we still need a list-based syntax to close the gap.
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9270 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:43:34 UTC