- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Apr 2022 17:04:22 +0000
- To: public-css-archive@w3.org
We ran out of time, but at the end of the discussion I suggested just censoring NaN to 0, if it's `infinity` specifically that's the issue (and not the more general censoring approach). It's just as likely to break a page, tho in a way that's possibly less disruptive (likely less scrollbars!), and it retains the simplicity of the current censoring, as opposed to the complexity of trying to define IACVT for used-value time. This seemed to make a lot of people in IRC happier, so for next week, proposed resolution is we change the NaN censoring behavior to turn it into a 0. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7067#issuecomment-1104189991 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 April 2022 17:04:23 UTC