- From: chcunningham via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Dec 2021 23:56:20 +0000
- To: public-css-archive@w3.org
This proposal was discussed in today's call. [Full transcript here](https://github.com/w3c/csswg-drafts/issues/5044#issuecomment-995006227). Let me respond to some points: > <fantasai> smfr: imagine you have two screens, right hand is dedicated to video presentation > <fantasai> smfr: somehow magically when you present video, it shows up on the right > <fantasai> smfr: but window object is associated with the left hand screen > <fantasai> smfr: so would be weird if it reported characteristics of right hand screen > <fantasai> ???: Is this possible today? > <fantasai> smfr: UA thing, UA could decide to send fullscreen video to a particular screen ... > <fantasai> florian: a browser could have two different videos on different screens, but that's a very different setup than here > <fantasai> smfr: I understand, I just don't want us to design a problem for foldables I think this idea to relocate fullscreen video won't work because most streaming sites actually fullscreen a div containing the video to allow for custom controls. > <fantasai> florian: This isn't necessarily about fullscreen video. > <fantasai> florian: if you have youtube playing in the middle of your web page, you would apply this ratio within the video > <fantasai> smfr: No, I don't think so, I think it only applies to fullscreen > ... > <fantasai> smfr: I think we should ask experts for feedback @jpiesing (TV expert) indicated that this is not just about full screen in https://github.com/w3c/csswg-drafts/issues/5044#issuecomment-723032003. > <fantasai> smfr: I think it would be very confusing for author @smfr, can you say more about the confusion? Streaming sites are already be accustomed to listening for changes to the element size and/or fullscreen events as a trigger to adapt content resolution. -- GitHub Notification of comment by chcunningham Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6891#issuecomment-995308811 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 December 2021 23:56:22 UTC