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

[csswg-drafts] [css-env] should we be requiring all env() variables in the spec to be implemented simultaneously?

From: Cameron McCormack via GitHub <sysbot+gh@w3.org>
Date: Fri, 06 Jul 2018 05:15:09 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-338807891-1530854108-sysbot+gh@w3.org>
heycam has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-env] should we be requiring all env() variables in the spec to be implemented simultaneously? ==
https://drafts.csswg.org/css-env-1

Currently the spec says:

> The following UA-defined environment variables are officially defined and must be supported [...]

Should we be making this requirement?  I think we generally don't require implementation of specific sets of CSS features.  We allow implementations to add support for features where they see fit.  So maybe we should be changing this wording (now that #2820 has agreement) to say something like "Here are the env() variables we have defined. You must not support other ones, but here are the behaviors of the ones that may be supported."

Alternatively we may want to allow groups of env() variables to all be supported if one of them is, such as all of the safe-area-inset-* ones.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2888 using your GitHub account
Received on Friday, 6 July 2018 05:15:22 UTC

This archive was generated by hypermail 2.3.1 : Friday, 6 July 2018 05:15:23 UTC