- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Aug 2021 17:36:16 +0000
- To: public-css-archive@w3.org
Right, as per those issues you linked in your edit, [leading (and trailing) whitespace is trimmed by the Syntax spec](https://drafts.csswg.org/css-syntax/#consume-declaration) before anything else has a chance to see the value, and then the serialization algo puts a single space after the colon before the property value. So Firefox is correct. > Does the intended change(s) in the spec(s) mean that a CSS component value can be a string in case the specified value is a var()-containing value? I'm sorry, I'm not quite sure what you mean by this question. Could you elaborate? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6484#issuecomment-905736427 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 August 2021 17:36:18 UTC