- From: Oriol Brufau via GitHub <noreply@w3.org>
- Date: Mon, 06 Apr 2026 00:17:00 +0000
- To: public-css-archive@w3.org
> If the [`<declaration-value>`](https://drafts.csswg.org/css-syntax-3/#typedef-declaration-value) is omitted, it represents an empty value. Presumably having a custom environment variable with an empty value is different than if it doesn't exist? E.g. with `param(--foo,)` ```css fill: green env(--foo); /* green */ fill: green env(--bar); /* invalid at computed-value time */ ``` Just like with `var()`: ```css --foo:; background: green var(--foo); /* green */ background: green var(--bar); /* invalid at computed-value time */ ``` -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13767#issuecomment-4189786887 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 April 2026 00:17:01 UTC