- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Jul 2019 00:06:16 +0000
- To: public-houdini-archive@w3.org
Hmmm, losing the reification behavior sucks. :( It means there's no way to interact with, say, a `"<length>"`-registered property as a CSSUnitValue, unless you go parse it yourself with your own knowledge. Is there any way we can save this? It'll require flushing style data and be racy with stylesheets, unfortunately. Even if we don't think it's reasonable to salvage `.get()`'s reification behavior, I'd want *some* way to say "reify this as --foo property specifies". But anything we add will *also* be racy. We can't even rely on, say, using a promise that doesn't resolve until the property is registered, since there might be multiple registrations. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/pull/912#issuecomment-508592991 using your GitHub account
Received on Friday, 5 July 2019 00:06:17 UTC