- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Oct 2016 04:02:46 +0000
- To: public-houdini-archive@w3.org
Just to clarify, is this thread discussing whether giving a type of a property does: (a) only cascades declarations that match and would animate according to the type provide, and eventually transition the property based on this type, or (b) all of the above, plus that var() declarations referencing the property needs to accept any value that the referenced custom property could accept to be valid, otherwise it is considered invalid at parse time? If that is the case: I remember my initial custom properties spec had something close to (b) to validate ```var(..., fallback)``` based on the fallback, but that has been rejected. I am not against validating the substitution at parse time, but if we validate the variable side for absolute correctness I think we also should validate the fallback for consistency, something we currently don't do. As such, I would lean towards (a) given the current design of ```var()```. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/321#issuecomment-253961112 using your GitHub account
Received on Saturday, 15 October 2016 04:02:53 UTC