- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Jun 2017 18:05:00 +0000
- To: public-css-archive@w3.org
Current text is: > Parse-time range-checking of values is not performed within ''calc()'', > and therefore out-of-range values do not cause the declaration to become invalid. > However, the used value resulting from an expression > must be clamped to the range allowed in the target context. I propose we change this to: > Parse-time range-checking of value is not performed within ''calc()'', > and therefore out-of-range values do not cause the declaration to become invalid. > However, at the point in the value computation process where the ''calc()'' can be resolved to a single term, > it must be clamped to the ranged allowed in the target context. > (For example, 'font-size' can resolve ''calc(10% - 1em)'' to a single term at computed-value time > (to -.9em, as it turns out), > which will then clamp to ''calc(0)''. > ''width: calc(10% - 1em)'', on the other hand, > can't resolve into a single term until used-value time.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/434#issuecomment-307459369 using your GitHub account
Received on Friday, 9 June 2017 18:05:06 UTC