W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-variables] should "--" be a valid custom property name?

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 06 Jun 2018 23:42:14 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-395247646-1528328534-sysbot+gh@w3.org>
The Working Group just discussed `should "--" be a valid custom property name?`, and agreed to the following:

* `RESOLVED: Reserve -- for future use and it is not a valid custom property name`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: should "--" be a valid custom property name?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2692<br>
&lt;dael> TabAtkins: Custom property names is anything starting with -- including -- by itself. I had intended to make a variable specific version of the all property and to claimm the -- name for it.<br>
&lt;dael> TabAtkins: Browsers allow -- as a custom property. I expect it's rare. I propose we officially disallow -- as a custom property name and add -- as an 'all' eq for variables<br>
&lt;AmeliaBR> Making `--` an official part of the spec sounds kind of horrible, so I don't like that reason for disallowing author use!<br>
&lt;tantek_> +1 on TabAtkins proposal, seems reasonable<br>
&lt;dael> TabAtkins: Only compat is if someone is using a plain -- and I suspect most people don't even know it's valid.<br>
&lt;AmeliaBR> (But I'm still happy to disallow it for author use.)<br>
&lt;dael> astearns: Let's separate proposed future use from the current point of disallowing.<br>
&lt;tantek_> +1 on reserving it for possible future use that is<br>
&lt;dael> astearns: You ccan disagree with using -- with how TabAtkins has suggested and still be okay to disallow.<br>
&lt;dael> TabAtkins: I don't see why disallow if not using it for something in the future.<br>
&lt;dael> tantek_: [missed] disallow because it shows up in html with a meaning. It feels like it is throw away syntax rather then have meaning. To keep a bit of line noise out of stylesheets<br>
&lt;fantasai> +1 on reserving for possible future use from me as well<br>
&lt;dael> fremy: I wanted to say I reviewed and I'm fine with TabAtkins proposal. My PoV this is a good change<br>
&lt;tantek_> Let's resolve on just the first half. We can defer debating if it means anything in the future<br>
&lt;dael> astearns: Objections to reserve -- for future use?<br>
&lt;dael> RESOLVED: Reserve -- for future use and it is not a valid custom property name<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2692#issuecomment-395247646 using your GitHub account
Received on Wednesday, 6 June 2018 23:42:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 June 2018 23:42:17 UTC