[css-2025][css-env-1] Add `env(safe-area-inset-*)` to Safe to Release exceptions

[SebastianZ]

Splitting the discussion from #10687 for adding the env() function together with the safe-area-inset-* keywords from CSS Environment Variables 1 to the Safe to Release pre-CR Exceptions section of the CSS Snapshot 2025.

Data to consider:

• Spec. status: ED (requires to publish a FPWD, see [css-env] Publish FPWD? #6729)
• implemented in all major browsers since 2020
• WPT: passing tests (experimental): Chrome: 42, Edge: 42, Firefox: 37, Safari: 37; interop: 37 / 42 (88.1%)
• Open issues: on GitHub: ~5, in spec.: 5

Summary: Very high interoperability, some open issues

Sebastian

[css-meeting-bot]

The CSS Working Group just discussed [css-2025][css-env-1] Add `env(safe-area-inset-*)` to Safe to Release exceptions.

The full IRC log of that discussion

<florian> SebastianZ: spec is not published yet, not even FPWD, but there's already an issue for the 6729
<ChrisL> q+
<florian> florian: interop is at 88%
<florian> s/issue for the/issue for that
<astearns> ack ChrisL
<florian> SebastianZ: 10 issues in total
<florian> ChrisL: this has been blocked from FPWD from 2021 because of a request on Apple to submit a list of env features, which seems wasn't done
<florian> ChrisL: there seems to be contention on the list
<fantasai> https://github.com//issues/11899
<florian> fantasai: we should circle back on that
<florian> ChrisL: we should decide if we add or not, but either way, we should do a FPWD
<florian> astearns: and then we can add to the snapshot
<florian> astearns: it's safer to wait