- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jun 2019 22:03:09 +0000
- To: public-houdini-archive@w3.org
Hmmmmmmmm. I think we need to think over this list to answer the question fully, tho. There are some stacked decisions here that we might be able to more fully unwind if we're revisiting decisions. To the point: if we give up on invalidation *entirely* (deferring all of it to computed-value time), then why don't we have the ability to unregister a property? It seems like we'd be free to allow it, then. (I'm pretty sure we chunked that because of invalidation, originally, if I recall correctly.) And if *that's* the case, then all the questions up above suddenly answer themselves: the `@property` rules just cascade normally, with last-in-stylesheet-order winning. Effectively each rule unregisters any previous instance of the name then registers itself. I am quite interested in seeing `@property` exist; I'd be willing to give up on TypedOM invalidation if that's what it took to have this all make sense. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/902#issuecomment-504216104 using your GitHub account
Received on Thursday, 20 June 2019 22:04:57 UTC