- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Oct 2022 15:47:06 +0000
- To: public-css-archive@w3.org
> Generally, the css-values specification suggest simplification: https://w3c.github.io/csswg-drafts/css-values-4/#calc-simplification "Simplification" as described there doesn't include clamping, though, does it? In [8.1.4. Range Checking](https://drafts.csswg.org/css-values-3/#calc-range), we read: > Parse-time range-checking of values is not performed within [calc()](https://drafts.csswg.org/css-values-3/#funcdef-calc), and therefore out-of-range values do not cause the declaration to become invalid. However, the value resulting from an expression must be clamped to the range allowed in the target context. Clamping is performed on [computed values](https://drafts.csswg.org/css-cascade-5/#computed-value) to the extent possible, and also on [used values](https://drafts.csswg.org/css-cascade-5/#used-value) if computation was unable to sufficiently simplify the expression to allow range-checking. (Clamping is not performed on [specified values](https://drafts.csswg.org/css-cascade-5/#specified-value).) So I guess the answer depends whether the serialized values of these descriptors are treated like *specified* or *used* values. I'm not sure what that means in relation to `@font-face` descriptors (as opposed to CSS properties). Is there a general convention for this, or do we need to specify it in each case? -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7964#issuecomment-1293732980 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 October 2022 15:47:08 UTC