- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jun 2019 07:44:06 +0000
- To: public-houdini-archive@w3.org
andruud has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-properties-values-api] @property vs setProperty == Given an `@property` rule in some stylesheet, how should the two-param `setProperty()`/`CSS.supports()` behave? They probably need to take into account the registration caused by the `@property` rule, even if that registration has not yet been effectuated. Updating "style data" (as @emilio [calls it in this comment](https://github.com/w3c/css-houdini-drafts/pull/847#issuecomment-502497184)) during `setProperty()` seems nasty. Do we revisit #880? Give up on `@property`? Accept the nastiness? Something else? cc @tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/902 using your GitHub account
Received on Monday, 17 June 2019 07:44:07 UTC