Re: [csswg-drafts] [css-sizing] Where does the default aspect-ratio of a <video> come from? (#12053)

The CSS Working Group just discussed `[css-sizing] Where does the default aspect-ratio of a <video> come from?`, and agreed to the following:

* `RESOLVED: No change`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> iank_: a few years ago when we worked on aspect-ratio<br>
&lt;kbabbitt> ... we had an issue in 7524<br>
&lt;kbabbitt> ... resolved for video element aspect ratio auto<br>
&lt;kbabbitt> ... to not pull from object size<br>
&lt;kbabbitt> ... Blink didn't implement initially but other 2 browsers did<br>
&lt;kbabbitt> ... as far as I can tell, other browsers did something different to resolution<br>
&lt;kbabbitt> ... all browsers at the moment, if you set explicit width and nothing else, explicit aspect ratio of 2:1<br>
&lt;fantasai> s/object size/default object size/<br>
&lt;kbabbitt> ... this issue is: is my interpretation that all browsers are rendering incorrectly, correct?<br>
&lt;kbabbitt> ... 2 possibilities<br>
&lt;kbabbitt> ... either should not have aspect ratio by default<br>
&lt;kbabbitt> ... interested to hear if other browsers ran into that<br>
&lt;kbabbitt> ... currently Chrome Canary has behavior from previous issue<br>
&lt;kbabbitt> ... other possibility is option 3 in the issue<br>
&lt;kbabbitt> ... the magic 2:1 aspect ratio out of somewhere<br>
&lt;kbabbitt> ... curious to hear from webkit or gecko folks<br>
&lt;kbabbitt> ... what they ran into when trying to implement previous resolution<br>
&lt;sgill> q+<br>
&lt;kbabbitt> Rossen6: feedback?<br>
&lt;kbabbitt> sgill: I worked on that issue from a few years ago<br>
&lt;Rossen6> ack sgill<br>
&lt;kbabbitt> ... don't quite remember all details, but issue you created and details in there I agree with<br>
&lt;kbabbitt> ... what you said in the issue is right, that rendering should be as you described<br>
&lt;kbabbitt> iank_: so do you think that we should do webkit's behavior or chrome canary's behavior<br>
&lt;kbabbitt> sgill: chrome canary's behavior<br>
&lt;kbabbitt> iank_: happy with that, we can close the issue as no change and i'll report back if Chrome has any issue rolling this out<br>
&lt;kbabbitt> ... will let this roll out and then update 6-8 wpts relying on it<br>
&lt;kbabbitt> Rossen6: anyone else?<br>
&lt;kbabbitt> iank_: Proposed resolution is no change<br>
&lt;kbabbitt> RESOLVED: No change<br>
</details>


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


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

Received on Wednesday, 18 June 2025 16:32:03 UTC