- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jun 2019 00:00:58 +0000
- To: public-houdini-archive@w3.org
> 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.) Hmm ... unregistering also seems relatively unproblematic with the current state of things (though I may be missing something). Sure, it changes what's accepted by CSSOM/TypedOM, but why is that worse than the transition from not registered to registered in the first place? > I am quite interested in seeing `@property` exist Yeah, me too. There's a real chance `@property` will never happen if this issue remains, that's what's bothering me. I personally care more about `@property` being a thing, vs. Typed OM invalidation, but that's me. (The current behavior is enabled in Chrome Beta at the moment, but now I'm leaning towards disabling it before it hits stable). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/902#issuecomment-504240470 using your GitHub account
Received on Friday, 21 June 2019 00:01:01 UTC