- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Aug 2023 16:57:56 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-color-4] Computed value and serialization of `Infinity` and `NaN` in color functions``, and agreed to the following: * `RESOLVED: No (further) change` <details><summary>The full IRC log of that discussion</summary> <fantasai> TabAtkins: Question was about if understanding of how infinity and nan showing up in color functions should be serialized at various value stages (and handled in general)<br> <fantasai> TabAtkins: does run into question of whether to do earlier reolution for color functions<br> <fantasai> TabAtkins: but aside from that<br> <fantasai> TabAtkins: if you put an infinite calculation into an rgba(), the behavior is well-defined: clamp to the allowed range<br> <fantasai> TabAtkins: I think for rgba() it's 0-255<br> <fantasai> TabAtkins: at at least computed value time<br> <fantasai> TabAtkins: specified value time is separate issue<br> <fantasai> TabAtkins: negative infinity clamps to zero<br> <fantasai> TabAtkins: and NaN becomes zero when it escapes a calculation teree<br> <fantasai> TabAtkins: that's all defined now<br> <fantasai> TabAtkins: so unless there is any disagreement on these cases, we can confirm no change<br> <fantasai> TabAtkins: and close the issue<br> <fantasai> TabAtkins: only thing left is separate issue of whether we eagerly simplify certain math functions in some cases<br> <fantasai> TabAtkins: but that's a separate issue<br> <fantasai> fantasai: separate isssue is filed?<br> <fantasai> TabAtkins: yes<br> <fantasai> Rossen_: proposed resolution is no (further) chagne<br> <fantasai> s/chagne/change/<br> <TabAtkins> (the separate issue is #8318)<br> <fantasai> RESOLVED: No (further) change<br> <TabAtkins> (#4 on the agenda this week, we skipped it because no Chris)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8629#issuecomment-1671807490 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 August 2023 16:57:57 UTC