Skip to content

[css-properties-values-api] Registering a property should cause us to validate var() fallback #360

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

Closed
tabatkins opened this issue Feb 14, 2017 · 1 comment

Comments

@tabatkins
Copy link
Member

In #321 (comment) the issue of var() fallback for typed variables is brought up. We should probably cause var() to be invalid-at-computed-value-time if its fallback doesn't match its registered grammar (regardless of whether or not the fallback is being used). Actually setting the custom property to a value that doesn't match its grammar does this already, so this makes the fallback work a little more consistently.

@FremyCompany
Copy link
Contributor

+1

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

No branches or pull requests

3 participants