Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[css-env-1] built-in env() features must go through CSSWG's standardization process #2820
This is an official statement from Mozilla regarding the proposed env() feature in css-env-1.
We think this ís a good feature in general, but we object to the following part:
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()
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
referenced this issue
Jul 3, 2018
The Working Group just discussed
The full IRC log of that discussion<fantasai> Topic: process for adding env() variables
<fantasai> github: https://github.com//issues/2820
<fantasai> TabAtkins: I agree.
<fantasai> astearns: Currently spec says “
<fantasai> user agents may define additional undocumented environment variables
<fantasai> TabAtkins: I think Apple agrees with proposal, too
<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
<fantasai> dino: But I don't know if anyone still believes that
<fantasai> RESOLVED: Accept proposal in the issue.
<fantasai> “UA vendors MUST NOT expose built-in env() features to the web without going through that process”