Open Que-tin opened 5 months ago
Closest I've seen is "custom env", https://github.com/w3c/csswg-drafts/issues/2627#issuecomment-386932374.
There are also a few proposals for registering a bunch of custom properties (and their initial values) in a less verbose way.
make sure they don't get overwritten
Does that mean you want the first rule that sets a constant to determine the value, and any further attempts to (re)set the value should be ignored? E.g.:
@env { --foo: 10px; }
@env { --foo: 20px; }
div {
width: env(--foo); /* --10px */
}
Is there a reason that we don't constants in CSS yet?
I was looking trough the open issues and couldn't find a single one asking for it.
e.g. for stuff like font-families or theme independent colors like brand colors it would be great to have something like this to make sure they don't get overwritten.
The syntax could be similar to custom properties by replaying
-
with_
so__*
. These should also be allowed in@property
definitions.I'm not 100% sure whether there should also be a new function to access these constants or whether the underscore are enough to differentiate the two when using
var()
for both. Open for discussion.