W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2017

Re: [csswg-drafts] [css-variables] User Agent properties and variables

From: Jonathan Neal via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Sep 2017 19:38:19 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-330958309-1505936287-sysbot+gh@w3.org>
I have a few questions.

First, I am presuming the request included making it clear “*that there is no way for the developer to set these properties*”. And now, I see interest in doing the opposite. which is to make these properties settable. I also see interest in making these properties exposable to `@media`.

So, if these properties are settable, how do we distinguish the non-settable ones? The ol’ double-dash?

```
@env --foo 0px;

body {
  margin: env(--foo);
  padding: env(safe-area-inset);
}
```

That makes me wonder. If `env()` is no longer the distinguishing quality of being un-settable, then could we modify `var()` to support the same functionality?

```
@var --foo 0px;

body {
  margin: var(--foo);
  padding: var(safe-area-inset);
}
```

And if that is possible, would we need `@var` at that point? Would `@var` be needed to expose variables to `@media`?

Then, if these properties are assignable and also available to `@media`, might they create recursion?

```
@env --foo 0px;

@media( width > max(  ) {
  @env --foo 200vw;
}
```

-- 
GitHub Notification of comment by jonathantneal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1693#issuecomment-330958309 using your GitHub account
Received on Wednesday, 20 September 2017 19:38:17 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:18 UTC