- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Aug 2023 15:15:21 +0000
- To: public-css-archive@w3.org
> Yeah, I meant that if you can substitute arbitrary stuff into `@media` (...) with env(), then probably `@custom-media` isn't needed. Nor is `@custom-container`, nor `@custom-future-thing`
The current `@custom-media` is defined in such a way that they are boolean features when used. It is not a token or component value substitution.
```css
@custom-media --foo only screen and (min-width: 300px);
@media (prefers-color-scheme: dark) and (--foo) {}
```
Can the same be achieved with `env()`?
CSS authors really like being able to write `@media (--tablet) {}` with tooling.
`@media (min-width: env(--tablet-width))` won't be as handy.
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9206#issuecomment-1684066729 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 August 2023 15:15:23 UTC