Re: [csswg-drafts] [css-values] Make top-level NaN be invalid at computed value time instead of ∞ (#7067)

The CSS Working Group just discussed `[css-values] Make top-level NaN be invalid at computed value time instead of ∞`, and agreed to the following:

* `RESOLVED: NaN escaping calc() tree is coerced to zero`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: [css-values] Make top-level NaN be invalid at computed value time instead of ∞<br>
&lt;fantasai> github: [css-values] Make top-level NaN be invalid at computed value time instead of ∞<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/7067<br>
&lt;fantasai> TabAtkins: last week we discussed behavior of censoring NaNs when they escape calc()<br>
&lt;fantasai> TabAtkins: previously specced as infinity<br>
&lt;fantasai> TabAtkins: discussion seemed to conclude that censoring to zero would be acceptable<br>
&lt;fantasai> TabAtkins: Since then, comments in issue supporting that interpretation, for a variety of good reasons<br>
&lt;fantasai> TabAtkins: This works well enough for my purposes, so suggest to resolve that NaN resolves to zero when escaping a calc() tree<br>
&lt;fantasai> iank_: can you elaborate more?<br>
&lt;fantasai> iank_: Inside a calc() tree, if you've got something relatively nested that has 1/0 or something that will be a NaN<br>
&lt;fantasai> iank_: is that where it is coerced to zero?<br>
&lt;fantasai> iank_: or will it propagate up<br>
&lt;fantasai> TabAtkins: it propagates up, infecting most of the tree following IEEE rules<br>
&lt;fantasai> TabAtkins: almost the same as JS also<br>
&lt;fantasai> TabAtkins: as soon as you escape the top-level function, properties don't know how to deal, so turn it into zero<br>
&lt;fantasai> iank_: ok, thanks<br>
&lt;TabAtkins> s/1/0/<br>
&lt;tantek> sounds reasonable<br>
&lt;fantasai> RESOLVED: NaN escaping calc() tree is coerced to zero<br>
&lt;lea> +1<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7067#issuecomment-1111211295 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 27 April 2022 16:31:24 UTC