W3C home > Mailing lists > Public > www-style@w3.org > November 2014

Re: [mediaqueries] Media Source Extensions and device capabilities

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 18 Nov 2014 13:11:43 -0800
Message-ID: <CAAWBYDDUVsmy8taS3W6rVJ-7fJo0LSZLMSQ1zk7MSYa9vOQbJQ@mail.gmail.com>
To: Mark Watson <watsonm@netflix.com>
Cc: "L. David Baron" <dbaron@dbaron.org>, Florian Rivoal <florian@rivoal.net>, "www-style@w3.org" <www-style@w3.org>
On Tue, Nov 18, 2014 at 12:54 PM, Mark Watson <watsonm@netflix.com> wrote:
> On Tue, Nov 18, 2014 at 12:43 PM, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
>> Ah, if scripting is involved, this is easier.  window.devicePixelRatio
>> gives you the screen density on all webkit/blink/ff browsers (dunno
>> about IE).  You can then just measure the element normally using
>> existing JS APIs, and use those two pieces of information to figure
>> out what source to load.
> There are two issues with that approach:
> (1) I'm buffering ahead of time, so really I am interested in what the
> situation would be if the video went fullscreen

Ah, you're worried about the case where the browser itself isn't
full-screen, so the fullscreen video dimensions might be larger than
the browser window?

> (2) There are scenarios where video gets downscaled, most notably when
> output over HDMI (due to HDCP, yes, I know), and in these scenarios I am
> interested in the actual output resolution (after downscaling)

Hm, that's much weirder.  I don't know how easy/possible it is to
acquire that information in browser-land.  I assume it probably is,
but shrug.

Received on Tuesday, 18 November 2014 21:12:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:48 UTC