Re: [csswg-drafts] [css-variables] Whitespace-trimming and custom properties. (#6345)

The CSS Working Group just discussed `[css-variables] Whitespace-trimming and custom properties.`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-variables] Whitespace-trimming and custom properties.<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6345<br>
&lt;dael> emilio: This one; we resolved a while ago on trimming whitespace from decorations. TabAtkins pointed out some examples invalid in impl should be valid.<br>
&lt;dael> emilio: For system prop fallback there's no trimming. Felt odd when impl that if you're using fallback in computed you get whitespace but if the fallback you have a variable it's stringed.<br>
&lt;TabAtkins> q+<br>
&lt;dael> emilio: Trimming whitespace from fallback functions would be simpliest. I think in general makes sense<br>
&lt;dael> Rossen_: Feedback?<br>
&lt;leaverou_> q?<br>
&lt;Rossen_> ack TabAtkins<br>
&lt;dael> TabAtkins: Yes, we absolutely should. That this doesn't work is accident of css rules for comma omission. You have to omit comna when not separating but this is the case where lack of a thing can be a thing. Need something in var to set the exception that you can set a comma<br>
&lt;dael> emilio: fwiw it's very easy to impl<br>
&lt;dael> Rossen_: Other feedback? leaverou_ you're in issue?<br>
&lt;dael> leaverou_: I added my thoughts to issue. I support that change<br>
&lt;TabAtkins> `foo(--a,)` is currently syntacitcally invalid, and that is good for everything *but* `var()`<br>
&lt;dael> Rossen_: Obj to adding the spec proposal?<br>
&lt;dael> Resolved: Accept the proposal<br>
</details>


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


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

Received on Wednesday, 9 June 2021 16:39:39 UTC