- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Apr 2018 20:07:11 +0000
- To: public-css-archive@w3.org
Yes, the spec is very clear on this matter - it should be clamped to 1 at computed value time. It is definitely **not** invalid at computed value time; that's not even remotely related to calc(), it's a variables thing. It absolutely can't be a parse error, because in the general case you can have expressions that can't be resolved at parse time. (V&U 3's calc() doesn't have any of these for purely numeric expressions, so you *could* tell at parse time what the value would end up being, but now that we have unit algebra it's back to being generally undecidable.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2590#issuecomment-382125144 using your GitHub account
Received on Tuesday, 17 April 2018 20:07:16 UTC