-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cssom-view] Expose video plane pixel ratio #6891
Comments
This proposal was discussed in today's call. Full transcript here. Let me respond to some points:
I think this idea to relocate fullscreen video is problematic because most streaming sites actually fullscreen a div containing the video to allow for custom controls.
@jpiesing (TV expert) indicated that this is not just about full screen in #5044 (comment).
@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. |
Do devices with a separate video plane use that for inline video? |
TV devices do that, yes. The hardware then arranges for the video plane to be composited (with appropriate scaling) with the graphics plane when to produce the output for the display. |
Discussion started in #5044. The main idea is to expose the device pixel ratio for
<video>
, allowing authors to select an optimal content resolution. UAs on TV's and dongles will often have a distinct video "plane" with a higher device pixel ratio than reported bywindow.devicePixelRatio
.I propose adding
deviceVideoPixelRatio
toScreen
. Authors can then determine the "video" pixels of anything, including screen (width, height), window (availWidth, availHeigh), as well as inline. For example:full screen case
inline case
The text was updated successfully, but these errors were encountered: