- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Feb 2022 23:21:30 +0000
- To: public-css-archive@w3.org
To clarify the difference here, the two options look like…
A **feature-level** syntax might be a bit simpler from the spec/implementation side:
```css
@container card-component (style(--card: feature) and style(--mode: dark)) or style(background: maroon) { … }
```
But the current **higher-level** syntax provides a bit more sugar for authors, since the function is only required once, and can contain multiple `style()` conditions:
```css
@container card-component style(((--card: feature) and (--mode: dark)) or (background: maroon)) { … }
```
My thoughts:
- My preference is for the higher-level syntax sugar, but it's not a big difference, and there's no functionality at stake
- This decision would likely apply to any new non-size features added in the future (eg 'state queries')
--
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7073#issuecomment-1054806452 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 February 2022 23:21:31 UTC