[css-env] Publish FPWD?

[xfq]

https://drafts.csswg.org/css-env/

Many browser engines already support env(). Are we ready to publish a FPWD?

[MatsPalmgren]

Apple has still not submitted the env() features that they are shipping to the csswg for standardization (as they are required to do per the resolution in #2820).

AIUI, if css-env is published it would make Safari and all other webkit-based browsers non-compliant CSS UAs.

Also, given the vast number of open issues on this spec, I don't think it's anywhere near ready.

[svgeesus]

A vast number of open issues does not preclude FPWD.

However, lack of consensus on general direction or major features could preclude FPWD, on the grounds that the patent exclusion opportunity would thereby be wasted until CR.

[css-meeting-bot]

The CSS Working Group just discussed publish css environment variables fpwd.

The full IRC log of that discussion

<dholbert> topic: publish css environment variables fpwd
<astearns> github: https://github.com//issues/6729
<dholbert> TabAtkins, as noted in the issue, the only real problem is that apple has a whole bunch of env variables that have yet to be submitted to spec
<dholbert> TabAtkins, don't want to publish fpwd without knowledge of all the variables that exist in the wild
<dholbert> TabAtkins, both from a usability and a patent perspective
<fantasai> s/TabAtkins,/TabAtkins:/g
<fantasai> s/astearns,/astearns:/g
<fantasai> scribenick: fantasai
<fantasai> astearns: Looked like 4 additional environment variables not in the spec?
<fantasai> TabAtkins: more than 4
<fantasai> TabAtkins: Don't remember precise list...
<fantasai> TabAtkins: Are we looking for a list to resolve on?
<fantasai> astearns: Want to know scope of work to do to FPWD
<fantasai> TabAtkins: Get that list in the spec, and have WG approve the list
<fantasai> astearns: Anyone from Apple know whether list of shipping env variables are things that should go into the spec?
<fantasai> heycam: Didn't look at the spec, so unsure how it matches WebKit
<fantasai> heycam: but happy to take an action item to look into it
<fantasai> ACTION heycam: Come up with list of WebKit environment variables for standardization
<fantasai> astearns: open separate issue for adding the environment variables, pls
<dholbert> scribenick: dholbert

[backflip]

@heycam, if I'm reading the IRC log above correctly, there was a plan to create a list of WebKit environment variables for standardization. Do you know whether this was abandoned by any chance?

[svgeesus]

Looping back to this, looks like the Nov 2021 decision to publish FPWD never happened because it is gated on getting that list of WebKit environment variables into the spec.

[svgeesus]

@jensimmons it looks like, per WG discussion, this FPWD is gated on Apple supplying a list of WebKit environment variables.

[svgeesus]

Or, actually, we just need verification of the list in

• [css-env] Add environment variables defined in WebKit #11899

[AtkinsSJ]

env() looks like it should be an arbitrary substitution function but was written before that concept existed. Maybe it's worth defining it in terms of that before it's published?