- From: Bramus via GitHub <noreply@w3.org>
- Date: Mon, 15 Sep 2025 09:00:30 +0000
- To: public-css-archive@w3.org
> Having said that, we are not aware of any sites that have adopted these, so we are open to either renaming, or unshipping them.
I ran an HTTPArchive query checking for `env(fullscreen-*)` usage in the `['width', 'height', 'top', 'left', 'bottom', 'right', 'padding', 'margin']` properties:
```sql
CREATE TEMPORARY FUNCTION getIsUsingFullscreenEnvvars(css JSON)
RETURNS INT64
LANGUAGE js
OPTIONS (library = "gs://httparchive/lib/css-utils.js")
AS '''
try {
function compute(ast) {
let detected = 0;
walkDeclarations(ast, ({property, value}) => {
const pattern = /env(\\s)*\\((\\s)*fullscreen/;
detected += pattern.test(value);
}, {
properties: ['width', 'height', 'top', 'left', 'bottom', 'right', 'padding', 'margin']
});
return detected;
}
return compute(css);
} catch (e) {
return null;
}
''';
SELECT
COUNT(DISTINCT IF(num_matches > 0, page, NULL)) AS pages,
COUNT(DISTINCT page) AS total,
COUNT(DISTINCT IF(num_matches > 0, page, NULL)) / GREATEST(COUNT(DISTINCT page), 1) AS pct
FROM (
SELECT
page,
url,
getIsUsingFullscreenEnvvars(css) AS num_matches
FROM
`httparchive.latest.parsed_css`
WHERE
is_root_page
)
```
Out of the 16,119,805 scanned entries, exactly 0 _(zero)_ CSS files are using the `env(fullscreen-*)` pattern for those properties.
I believe it would be safe for WebKit to unship these properties _(like @smfr [mentioned](https://github.com/w3c/csswg-drafts/issues/11899#issuecomment-3275972813))_, and for the CSSWG to not specify these `fullscreen-*` envvars.
PROPOSED RESOLUTION: Do not add the `fullscreen-*` envvars.
--
GitHub Notification of comment by bramus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11899#issuecomment-3291129278 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 September 2025 09:01:02 UTC