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

> I'm pretty sure we chunked that because of invalidation, originally, if I recall correctly.

For reference, here's the log with that decision: https://logs.csswg.org/irc.w3.org/houdini/2016-09-22/#e727846

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

It seems like it. :neutral_face: 

> 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).

That's an interesting proposal! This is #845, BTW.

There is also #846, though that issue is probably not unique to `@property`.

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

Received on Friday, 21 June 2019 09:45:28 UTC