Re: [csswg-drafts] [css-env] Add environment variables defined in WebKit (#11899)

The CSS Working Group just discussed `[css-env] Add environment variables defined in WebKit`, and agreed to the following:

* `RESOLVED: drop the fullscreen-* vars`
* `RESOLVED: publish FPWD css-env-1`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> SebastianZ: we wanted to publish fpwd of css-env-1<br>
&lt;kbabbitt> ... we had 1 issue that is blocking publication which is deciding whether to add the variables defined in webkkit to the spec or not<br>
&lt;bramus> q+<br>
&lt;Rossen4> q?<br>
&lt;Rossen4> ack bramus<br>
&lt;kbabbitt> bramus: on the thread we looked into these env vars<br>
&lt;kbabbitt> ... smfr mentioned that they were introduced back in the day but they are not aware of any sites that have adopted<br>
&lt;kbabbitt> ... I ran a query on httparchive to be sure<br>
&lt;kbabbitt> ... checking for env(fullscreen-*) in width height etc.<br>
&lt;kbabbitt> ... result came back with 0 sites out of 16 million+ had it in CSS<br>
&lt;kbabbitt> ... which is quite reassuring<br>
&lt;kbabbitt> ... smfr also mentioned they are open to renaming or unshipping these properties<br>
&lt;kbabbitt> ... given 0 sites matched, I think unshipping is the answer<br>
&lt;kbabbitt> ... so not add to css-env spec<br>
&lt;ntim> q+<br>
&lt;kbabbitt> Rossen4: seems like a reasonable proposal<br>
&lt;kbabbitt> ntim: I think it's reasonable<br>
&lt;kbabbitt> ... even if there are some use cases for this env var we probably want to rename anyway<br>
&lt;kbabbitt> ... for now removing it is the right call<br>
&lt;kbabbitt> +1<br>
&lt;kbabbitt> Rossen4: let's try to resolve<br>
&lt;kbabbitt> ... any objections to dropping this list of env vars that are webkit specific from the spec?<br>
&lt;emeyer> +1<br>
&lt;kbabbitt> PROPOSED: drop the fullscreen-* vars<br>
&lt;kbabbitt> RESOLVED: drop the fullscreen-* vars<br>
&lt;kbabbitt> Rossen4: SebastianZ do you have a resolution to republish?<br>
&lt;kbabbitt> SebastianZ: It would be republish or publish, don't remember if we have one<br>
&lt;kbabbitt> Rossen4: any objection to publishing?<br>
&lt;kbabbitt> SebastianZ: this would be level 1<br>
&lt;kbabbitt> Rossen4: FPWD of css-env-1<br>
&lt;kbabbitt> Rossen4: since this is first public I'd like to have attention and make sure we're ready to publish<br>
&lt;kbabbitt> fantasai: as long as TabAtkins has reviewed and think it's complete, it's fine<br>
&lt;kbabbitt> TabAtkins: yes I think we should go for it<br>
&lt;kbabbitt> Rossen4: objections?<br>
&lt;kbabbitt> RESOLVED: publish FPWD css-env-1<br>
&lt;bramus> Yay!<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11899#issuecomment-3303695230 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 September 2025 16:12:31 UTC