- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jul 2019 05:00:27 +0000
- To: public-houdini-archive@w3.org
> potentially bringing back to life declarations that were overridden [...] from nowhere Yeah, I know ... we can't do that. > I think "operations such that it would affect values that are already parsed" is also pretty hard to detect for the same reason. It could be more defensive, like "insertions/deletions of `@property` rules affecting a custom property that has been used anywhere, once, ever". This specifically might not be what we want ... but I think if we want these properties to behave natively ( would be nice, right? :-) ), we'd need to define the properties outside the "regular author scope" of CSS, or limit how/when `@property` rules appear (which can have almost the same effect). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/pull/912#issuecomment-512102591 using your GitHub account
Received on Wednesday, 17 July 2019 05:00:28 UTC