Re: [csswg-drafts] [css-syntax] Trim whitespace around declarations?

The CSS Working Group just discussed `[css-syntax] Trim whitespace around declarations?`, and agreed to the following resolutions:

* `RESOLVED: trim white space before / after property value in a declaration.`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: [css-syntax] Trim whitespace around declarations?<br>
&lt;astearns> github topic: [css-syntax] Trim whitespace around declarations?<br>
&lt;astearns> github topic: https://github.com/w3c/csswg-drafts/issues/774<br>
&lt;fantasai> TabAtkins: This has impact on what custom property values are<br>
&lt;fantasai> TabAtkins: Because custom properties capture tokens<br>
&lt;fantasai> TabAtkins: Currently the white space before first value token is preserved<br>
&lt;fantasai> TabAtkins: All of the normal properties serialize out from OM, so they get normalized white space output<br>
&lt;fantasai> TabAtkins: Some people brought up maybe we should trim the white space from beginning and end of a token stream<br>
&lt;fantasai> TabAtkins: This would be a tweak to the Syntax spec<br>
&lt;fantasai> TabAtkins: to throw away this white space<br>
&lt;fantasai> TabAtkins: No consequence for ordinary CSS, they will continue to parse and serialize as usual<br>
&lt;fantasai> TabAtkins: It may or may not have an observable difference on serializing a rule of a style sheet... I think they generally reserialize from internal structures<br>
&lt;gregwhitworth> basically this saves authors from writing trim() when manipulating custom props<br>
&lt;fantasai> TabAtkins: Would have desired difference on serialization of custom property value when ppl write with typical whitespace after colon<br>
&lt;fantasai> TabAtkins: Saves authors from writing trim(), right, and also from forgetting to write trim() because they never have to write that for any other property<br>
&lt;fantasai> leaverou: Is there any use case where you want the white space<br>
&lt;fantasai> TabAtkins: If you're embedding an esoteric language...<br>
&lt;fantasai> TabAtkins: If you're embedding another programming language into CSS you'll have consequences anyway<br>
&lt;fantasai> TabAtkins: Don't think any other issue<br>
&lt;fantasai> leaverou: So benefit to it, and not hurting any use case. So I'm hugely in favor.<br>
&lt;fantasai> leaverou: Every time I use OM for custom properties, have to use trim(), it's really annoying.<br>
&lt;ChrisL> +1 to trimming<br>
&lt;fantasai> astearns: Proposal to trim whitespace on either side of all declarations. In favor / opposed?<br>
&lt;fantasai> RESOLVED: trim white space before / after property value in a declaration.<br>
</details>


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

Received on Wednesday, 5 July 2017 23:50:25 UTC