New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
MatsPalmgren opened this Issue Jun 26, 2018 · 1 comment

Comments

Projects
None yet
4 participants
@MatsPalmgren

MatsPalmgren commented Jun 26, 2018

Dear CSSWG,

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:

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.

@css-meeting-bot

This comment has been minimized.

Member

css-meeting-bot commented Jul 4, 2018

The Working Group just discussed process for adding env() variables, and agreed to the following:

  • RESOLVED: Accept proposal in the issue.
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> ”
<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”
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment