- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Jul 2019 07:50:25 +0000
- To: public-css-archive@w3.org
> Right? Right! :-) And that behavior is already defined by the spec as-is (I think). Though it might be good to be a bit more clear on the distinction between iacvt and cyclic. Related bonus information worth keeping in mind: [standard properties can also participate in a cycle](https://drafts.css-houdini.org/css-properties-values-api-1/#dependency-cycles), but they can't be "guaranteed-invalid", so they'll have to get `unset` in both iacvt and the cyclic case. This slightly "pollutes" the otherwise clean separation between iacvt and cyclic, unfortunately ... not a huge deal, though. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4075#issuecomment-511706761 using your GitHub account
Received on Tuesday, 16 July 2019 07:50:28 UTC