Re: [csswg-drafts] [cssom-view] should screen.width and screen.height reflect orientation? (#5204)

The CSS Working Group just discussed `[cssom-view] should screen.width and screen.height reflect orientation?`, and agreed to the following:

* `RESOLVED: screen.width/height should change based on orientation changes`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> smfr: screen.width and .height reflect rotation in Chrome on Android, they do not on safari iOS<br>
&lt;TabAtkins> smfr: logical in Chrome, physical in safari<br>
&lt;TabAtkins> smfr: I think ti probably makes sense to change on rotation. we're willing to experiment, compat is a potential concern<br>
&lt;flackr> q+<br>
&lt;florian> q+<br>
&lt;astearns> ack flackr<br>
&lt;TabAtkins> +1, I think these should be logical<br>
&lt;ydaniv> +1<br>
&lt;TabAtkins> flackr: I think they should change. they still correspond to the physical screen, just in the orientation that's currently being used<br>
&lt;iank_> (we are likely compat constrained as well - if we were to change)<br>
&lt;astearns> ack florian<br>
&lt;TabAtkins> flackr: there's some change in the dimensions based on what areas you're allowed to change<br>
&lt;TabAtkins> florian: so this is screen, not window. this is allowed to not be reported at all, right? so for fingerprinting, it could be hidden entirely, but as long as it's reported it should be useful<br>
&lt;TabAtkins> florian: so either you shouldn't report them at all (for privacy or something), or you flip them with the screen so they're useful<br>
&lt;TabAtkins> astearns: so proposed resolution is screen.width/height should change based on orientation changes<br>
&lt;TabAtkins> (same as width/height MQs, necessary I think)<br>
&lt;TabAtkins> RESOLVED: screen.width/height should change based on orientation changes<br>
&lt;fantasai> scribe+<br>
</details>


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


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

Received on Wednesday, 23 July 2025 16:53:40 UTC