Re: [css-houdini-drafts] [css-typed-om] CSSUnparsedValue constructor behaviour if arguments are not alternating

That statement is just wrong in the first place - I think `--foo:var(bar)var(baz);` would have two variables references in a row, without a string in the middle. (Theoretically we could put an empty string there, but why?)  I should remove it.

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

Received on Thursday, 2 November 2017 20:47:47 UTC