- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 18 Jun 2025 16:32:02 +0000
- To: public-css-archive@w3.org
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> <kbabbitt> iank_: a few years ago when we worked on aspect-ratio<br> <kbabbitt> ... we had an issue in 7524<br> <kbabbitt> ... resolved for video element aspect ratio auto<br> <kbabbitt> ... to not pull from object size<br> <kbabbitt> ... Blink didn't implement initially but other 2 browsers did<br> <kbabbitt> ... as far as I can tell, other browsers did something different to resolution<br> <kbabbitt> ... all browsers at the moment, if you set explicit width and nothing else, explicit aspect ratio of 2:1<br> <fantasai> s/object size/default object size/<br> <kbabbitt> ... this issue is: is my interpretation that all browsers are rendering incorrectly, correct?<br> <kbabbitt> ... 2 possibilities<br> <kbabbitt> ... either should not have aspect ratio by default<br> <kbabbitt> ... interested to hear if other browsers ran into that<br> <kbabbitt> ... currently Chrome Canary has behavior from previous issue<br> <kbabbitt> ... other possibility is option 3 in the issue<br> <kbabbitt> ... the magic 2:1 aspect ratio out of somewhere<br> <kbabbitt> ... curious to hear from webkit or gecko folks<br> <kbabbitt> ... what they ran into when trying to implement previous resolution<br> <sgill> q+<br> <kbabbitt> Rossen6: feedback?<br> <kbabbitt> sgill: I worked on that issue from a few years ago<br> <Rossen6> ack sgill<br> <kbabbitt> ... don't quite remember all details, but issue you created and details in there I agree with<br> <kbabbitt> ... what you said in the issue is right, that rendering should be as you described<br> <kbabbitt> iank_: so do you think that we should do webkit's behavior or chrome canary's behavior<br> <kbabbitt> sgill: chrome canary's behavior<br> <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> <kbabbitt> ... will let this roll out and then update 6-8 wpts relying on it<br> <kbabbitt> Rossen6: anyone else?<br> <kbabbitt> iank_: Proposed resolution is no change<br> <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