- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Thu, 11 Sep 2025 11:28:24 +0000
- To: public-css-archive@w3.org
SebastianZ has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-2025][css-env-1] Add `env(safe-area-inset-*)` to Safe to Release exceptions == Splitting the discussion from #10687 for adding the [`env(safe-area-inset-*)` function](https://drafts.csswg.org/css-env-1/#env-function) from [CSS Environment Variables 1](https://drafts.csswg.org/css-env-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 #6729) * [implemented in all major browsers since 2020](https://developer.mozilla.org/en-US/docs/Web/CSS/env#browser_compatibility) * [WPT](https://wpt.fyi/results/css/css-env?label=master&label=experimental&aligned): passing tests (experimental): Chrome: 42, Edge: 42, Firefox: 37, Safari: 37; [interop](https://wpt.fyi/results/css/css-env?label=master&label=experimental&aligned&q=all(status%3Apass)): 37 / 42 (88.1%) * Open issues: [on GitHub](https://github.com/w3c/csswg-drafts/issues?q=is%3Aopen+is%3Aissue+label%3Acss-env-1+"env()"+"safe-area-inset"): ~5, [in spec.](https://drafts.csswg.org/css-env-1/#issues-index): 5 Summary: Very high interoperability, some open issues Sebastian Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12780 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 September 2025 11:28:25 UTC