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

Re: [csswg-drafts] [css-env-1] built-in env() features must go through CSSWG's standardization process

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Jul 2018 04:12:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402357806-1530677532-sysbot+gh@w3.org>
The Working Group just discussed `process for adding env() variables`, and agreed to the following:

* `RESOLVED: Accept proposal in the issue.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: process for adding env() variables<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/2820<br>
&lt;fantasai> TabAtkins: I agree.<br>
&lt;fantasai> astearns: Currently spec says “<br>
&lt;fantasai>     user agents may define additional undocumented environment variables<br>
&lt;fantasai> ”<br>
&lt;fantasai> TabAtkins: I think Apple agrees with proposal, too<br>
&lt;fantasai> dino: When original discussion happened, there was some mumblings that some platforms might want to expose system colors specific to that platform in some way<br>
&lt;fantasai> dino: But I don't know if anyone still believes that<br>
&lt;fantasai> RESOLVED: Accept proposal in the issue.<br>
&lt;fantasai> “UA vendors MUST NOT expose built-in env() features to the web without going through that process”<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2820#issuecomment-402357806 using your GitHub account
Received on Wednesday, 4 July 2018 04:12:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 July 2018 04:12:16 UTC