Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-properties-values-api-1] Should @property always be invalid with CSS-wide keywords or property substitutions for initial-value? #1130

Open
cdoublev opened this issue Oct 8, 2024 · 0 comments

Comments

@cdoublev
Copy link
Contributor

cdoublev commented Oct 8, 2024

There is this note about computationally independent values:

[...] 3em is not computationally independent [...]. Neither is a value with a var() function, because it relies on the value of a custom property.

Browsers make @property invalid with syntax: "<custom-ident>" and initial-value: initial (WPT) whereas initial is computationally independent. If initial cannot match <custom-ident>, neither can var(--custom). Both are valid property values, no matter the property value definition.

Similarly, syntax: "<length>" with initial-value: first-valid(1vmin, 20px) seems reasonable. But that might also not be allowed (cf. #1120).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant