- From: Jonathan Chan via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Aug 2017 19:25:30 +0000
- To: public-houdini-archive@w3.org
Before: If `syntax` is not "*" and `initialValue` is not specified, it defaults to an invalid empty value, per your comment in https://github.com/w3c/css-houdini-drafts/issues/286#issuecomment-246861212. Because you were disagreeing with heycam, I assumed you implied that an exception should not be thrown, and that this value should just trigger the "invalid at computed-value time" behavior when substituting, and be return when we get it through OM. After: If `syntax` is not "*" and `initialValue` is not specified, then syntax becomes `parsed syntax`. We do not go to the following case because `parsed syntax` is not undefined (i.e. `syntax` was "*" in step 3): > If parsed syntax is undefined, and initialValue is not present, let parsed initial value be empty. This must be treated identically to the "default" initial value of custom properties, as defined in [css-variables]. Skip to the next step of this algorithm. We do not go to the following case either, again because `parsed syntax` is not undefined: > Otherwise, if parsed syntax is undefined, parse initialValue as a <declaration-value>. If this fails, throw a SyntaxError and exit this algorithm. Otherwise, let parsed initial value be the parsed result. Skip to the next step of this algorithm. Instead, we go to this case: > Otherwise, if initialValue is not present, throw a SyntaxError and exit this algorithm. Which contradicts what you were saying about not throwing an exception. -- GitHub Notification of comment by jyc Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/286#issuecomment-323830078 using your GitHub account
Received on Monday, 21 August 2017 19:25:29 UTC