[go: up one dir, main page]

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-values] Clarify that <percentage>s never resolve to <number>s in calc() #2789

Closed
SebastianZ opened this issue Jun 15, 2018 · 1 comment

Comments

@SebastianZ
Copy link
Contributor

In issue #1463 it was resolved that <percentage> values never resolve to <number> values when used in calc(). Though the change made to the spec. isn't as clear as @tabatkins' description in the issue.
There it was said that the problem is that calc(1% * 1%) would be valid for opacity (as percentages resolve to <number>s, while it is invalid in width (as it would resolve to length²).

Furthermore, it missed that the definition of percentage values still allows combinations of <number> and <percentage> values in calc() saying

In cases where a <percentage> can represent the same quantity as a dimension or number in the same component value position, and can therefore be combined with them in a calc() expression…

This sentence should be rephrased, so that it's clear that <percentage> + <number> combinations are invalid within calc().

Sebastian

@SebastianZ
Copy link
Contributor Author

Btw., when you're at it, you should replace "Altho" by "Although" to be more formal and understandable.

Sebastian

fantasai added a commit that referenced this issue Oct 8, 2020
…ing <length-number> definition from L3 (see #2789 where it was resolved for L4).
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