- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Jun 2019 21:49:52 +0000
- To: public-houdini-archive@w3.org
> You mean we have to set the [[associatedProperty]] to the current property? Currently, yes. That algo requires you to pass a value *and* a property name. > What I wanted to do here (without quite knowing how), was catch the case where the underlying value is a value without additional type attached to it I don't quite understand what you mean by this. Can you elaborate? > Won't that cause `<color>` and other things that aren't explicitly mentioned to reify as a list of component values? I think we do need to fall back to direct CSSStyleValue in the general case. Or explicitly mention everything. Ah, yes, that's not what we want. Since `<color>` doesn't yet have a specialized type, it needs to reify as a CSSStyleValue associated with the custom property in question. That is indeed different from a list of component values. So yeah, then, step 6's condition should be "grammar isn't `*`", and then should "reify as a CSSStyleValue" for that custom property, then step 7 can handle the rest with a "reify as a list of component values". -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/897#issuecomment-498856635 using your GitHub account
Received on Tuesday, 4 June 2019 21:49:54 UTC