Re: [w3ctag/design-reviews] [CSS-Values-4] FYI review of Allow infinity, -infinity and NaN in CSS calc() (Issue #708)

@tabatkins spec editor in case I missed anything

The situation here is that:
- All `calc()` must be valid at parsing time, because parse-time value range checking is basically impossible
- Even if `calc()` result is NaN, we still need to make the CSS property value valid. We can't put a NaN there

So treating calc() result NaN as positive infinity looks like an arbitrarily chosen fallback to me.

Or would it better if we want to follow the same approach as custom properties that, any propety value involving a NaN `calc()` is invalid at computed time, and is resolved as `initial`/`inherit`? Or is it overengineering?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/708#issuecomment-1032123938
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/708/1032123938@github.com>