- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Feb 2017 18:34:25 +0000
- To: public-houdini-archive@w3.org
The original issue (should a property fail at parse-time if a typed custom property is used in a wrong way, per the property's grammar) is, I think, a no. I believe this falls out of our decision at the Seattle f2f (<https://github.com/w3c/css-houdini-drafts/issues/354>) that registering a custom property shouldn't require an immediate global re-parse. You can do wrong things to/with a typed custom property; it'll just cause a failure at computed-value time, like an untyped custom property with an incompatible value does. The later issue (should we validate the `var()` fallback for consistency with the property's type) is something we probably should do. I'll move it to a separate issue for better tracking, and go ahead and close this one. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/321#issuecomment-279794319 using your GitHub account
Received on Tuesday, 14 February 2017 18:34:32 UTC