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

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

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Tue, 26 Jun 2018 00:05:50 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-335610713-1529971549-sysbot+gh@w3.org>
MatsPalmgren has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-env-1] built-in env() features must go through CSSWG's standardization process ==
Dear CSSWG,

This is an official statement from Mozilla regarding the proposed env() feature in [css-env-1](https://drafts.csswg.org/css-env-1).

We think this ís a good feature in general, but we object to the following part:
> user agents may define additional undocumented environment variables

Allowing vendors to introduce arbitrary new features into the web platform like this has exactly the same problems as vendor-prefixed properties and values have, which as we all know, is the one of the biggest mistakes in CSS's history.

Our opinion is that all env() `<custom-ident>`s MUST be decided by CSSWG consensus using the same process that is used for introducing other CSS features.  That process has the following benefits:
1. there is a comprehensible specification for each `<custom-ident>`  so that anyone can implement it without having to reverse-engineer specific UAs
2. each feature gets proper privacy, security, a11y and i18n review
3. the W3C rules regarding patents apply
etc

UA vendors MUST NOT expose built-in env() features to the web without going through that process.  This process requirement should be written into the env() spec itself as a normative requirement on all built-in `<custom-ident>`s that are exposed to web content.



Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2820 using your GitHub account
Received on Tuesday, 26 June 2018 00:05:52 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:31 UTC