Open miragecraft opened 1 year ago
This should probably be in https://github.com/w3c/css-houdini-drafts/issues/
And I don't really understand what you are proposing.
And I don't really understand what you are proposing.
Currently, once you specify @property
for a custom property, you can no longer use a fallback value because @property
mandates an initial-value
if you define a syntax other than syntax: "*"
.
The initial-value
takes over the functionality of the fallback value.
This leaves two gaps in functionality:
initial-value
is defined once globally.@property
does not support it.
I'm experimenting with the new
@property
at-rule and feel that it should include the ability to usesyntax
in conjunction with custom property fallback value.For example, let's say I want to create a special
--width
custom property that accepts fractions (such as1/2
,2/5
) in addition to all the values allowed by the built-inwidth
property including the unitless0
,<percentage-length>
, as well as all the keywords such asauto
,min-content
,max-content
,fit-content
.Currently it's not possible to do so, but if we allow syntax checking with fallback, we can do:
So this is why I would like the spec to allow combining fallback with syntax checking.