- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2020 11:29:47 +0000
- To: public-houdini-archive@w3.org
@justinmichaud-2 The distinction between _invalid at computed-value time_ and _cyclic at computed-value time_ was [added to css-variables](https://github.com/w3c/csswg-drafts/commit/28cf15d0e12b2687b51087d9a23338bb14498c79) a while back. In additions, all browsers have now shipped a consistent behavior for treating IACVT as 'unset' in all cases (see https://github.com/w3c/csswg-drafts/issues/4075). Is this good enough to close this issue? -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/849#issuecomment-665610111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 July 2020 11:29:48 UTC