Re: [csswg-drafts] [css-typed-om-1] How should leading whitespace before var() be normalized in CSSUnparsedValue round-tripping? (#13792)

The CSS Working Group just discussed `[css-typed-om-1] How should leading whitespace before var() be normalized in CSSUnparsedValue round-tripping?`, and agreed to the following:

* `RESOLVED: Normalize whitespace even when the custom properties come from typed om`

<details><summary>The full IRC log of that discussion</summary>
&lt;flackr> emilio: this came up when implementing typed om in gecko. a while ago we added trimming so leading and trailing whitespace is removed<br>
&lt;flackr> emilio: it seems that in webkit/blink, you can sidestep this using typed om, which seems a bit weird<br>
&lt;flackr> emilio: when setting a property via typed om, I think we should also normalize whitespace just like we normalize calc expressions<br>
&lt;smfr> seems fine<br>
&lt;emilio> astearns: makes sense to me to normalize it in the same way<br>
&lt;fantasai> +1<br>
&lt;emilio> PROPOSAL: Normalize whitespace when the custom properties come from typed om<br>
&lt;emilio> RESOLVED: Normalize whitespace even when the custom properties come from typed om<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13792#issuecomment-4389554254 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 May 2026 15:22:53 UTC