- From: Mats Palmgren <mats@mozilla.com>
- Date: Tue, 26 Jun 2018 02:17:30 +0200
- To: www-style list <www-style@w3.org>
Dear CSSWG,
This is an official statement from Mozilla regarding the proposed
env() feature in https://drafts.csswg.org/css-env-1
We think this is 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.
We have filed this as a spec issue here:
https://github.com/w3c/csswg-drafts/issues/2820
Received on Tuesday, 26 June 2018 00:17:56 UTC