- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Aug 2021 06:28:44 +0000
- To: public-css-archive@w3.org
I notice that Firefox trims leading whitespace(s) of the original string and that other consecutive whitespace(s) are kept, (consecutive whitespaces are replaced by `__` in the following example, because the Markdown parser merges them) eg. `color:__var(__--blue__)__` becomes `color: var(__--blue__)__`. I know that leading whitespace(s) are trimmed when tokenizing but I do not know a procedure in CSSOM, CSS Syntax, or CSS Variable, that defines trimming leading whitespaces (before tokenizing), though. I understand that your intent is to define that the original string (and its leading whitespaces?) should be kept. To serialize a CSS value, the declaration value should be *represented as a list of CSS component values `components` that, when parsed according to the property’s grammar, would represent that value*, and a component value is defined as *one of the preserved tokens, a function, or a simple block*. 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? -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6484#issuecomment-905221740 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 06:28:46 UTC