Re: [css-houdini-drafts] [css-properties-values-api] @property vs setProperty (#902)

I agree with pretty much everything y'all have said. Unregistration also doesn't seem extremely problematic.

Giving up on typed om / setProperty invalidation is the easiest and simplest way to make this whole model make sense IMO.

The only other question then is, I'd think, what happens when script-registered and style-registered properties clash. I think the easiest solution to that problem is saying that they're independent (that is, you can't `unregisterProperty` a property registered via `@property`, and vice-versa, and then you just need to specify in which order do we look at the two sets if there's a name conflict).

-- 
GitHub Notification of comment by emilio
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/902#issuecomment-504331914 using your GitHub account

Received on Friday, 21 June 2019 08:00:21 UTC