W3C home > Mailing lists > Public > www-style@w3.org > March 2013

Re: [mediaqueries4] Media queries for multichannel audio ?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 20 Mar 2013 10:22:47 -0700
Message-ID: <CAAWBYDBjv5gq03H2yQ+NN0Yv6uZPhgr_0JjV+tt=KVeC8qq3ow@mail.gmail.com>
To: Mark Watson <watsonm@netflix.com>
Cc: Kenneth Rohde Christiansen <kenneth.r.christiansen@intel.com>, "florian@rivoal.net" <florian@rivoal.net>, "www-style@w3.org" <www-style@w3.org>
On Wed, Mar 20, 2013 at 10:19 AM, Mark Watson <watsonm@netflix.com> wrote:
> On Mar 20, 2013, at 10:10 AM, Tab Atkins Jr. wrote:
>> On Wed, Mar 20, 2013 at 8:37 AM, Mark Watson <watsonm@netflix.com> wrote:
>>> What I need is just the device width and height in device pixels, to know
>>> when it is not worth delivering a high resolution version of the content.
>>> It's not such a big deal with HD, since there are a dwindling number of SD
>>> displays, but with 4K this will be an issue.
>>
>> You don't want that.  What you want instead is some way to declare the
>> resolution on the <source> element, so (1) the browser can
>> intelligently choose which source to download, based on what it knows
>> about the display, the user's internet connection, and possibly other
>> things, and (2)  the browser can offer both options to the user, a la
>> YouTube's resolution selection.
>
> I'm interested in implementing the resource selection algorithm in
> Javascript for the case where I am using the Media Source Extensions, not
> the <source> element. See
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21336.

Forgive me for not finding that a compelling use-case.  ^_^

More seriously, if the EME stuff is so foreign that it can't even
integrate with the <video> source selection, that's a bug in the EME
spec, not something to be worked around in other specs.

~TJ
Received on Wednesday, 20 March 2013 17:23:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:07 GMT