Re: [css-houdini-drafts] [css-properties-values-api] [css-variables] Should the spec document invalid variables and fallback more explicitly? (#849)

What I find confusing, is that CSS Variables currently use the term "initial" to mean invalid-for-substitution-value. This is of course because the initial value for unregistered custom properties _always is_ the invalid-for-substitution-value, but it becomes confusing when the initial value can be something else.

Should probably go through CSS Variables, and make sure that it consistently uses the term "unset" when it means unset (i.e. invalid-for-substitution-value for unregistered properties, initial for non-inherited registered properties, and inherit for inherited registered properties), and "invalid value for substitution" (or something) when that's the intent.

-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/849#issuecomment-455475369 using your GitHub account

Received on Friday, 18 January 2019 09:06:01 UTC