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-values-5] Does serializing calc-size() ever change the number of arguments? #10259
Comments
I agree that this needs specification. I lean towards option 3; I agree that in general the two-arg form is clearer. |
I've implemented option 3 in Chromium. |
Though thinking about it a little more, I think perhaps another argument against option 3 is that, without it, authors basically never need to write the two-argument form. For most things authors want, they just want to wrap one or both of the endpoints of an animation in |
The definition of
calc-size()
doesn't mention serialization at all, and I think it probably should. In particular, the question I have about serialization is whether the number of arguments tocalc-size()
should ever change during a parse-serialize cycle. I think there are three options:Based on what
calc-size()
does I don't especially like option 1. General principles of CSS serialization probably don't like 3, since shorter forms are generally preferred. And since this question applies to both specified and computed values (though the answer could be different for the two), and option 2 is pretty strange for computed values, I also don't particularly like option 2.cc @tabatkins
The text was updated successfully, but these errors were encountered: