W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2010

Re: [media] a first draft JavaScript API for multitrack media

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 18 Feb 2010 16:39:17 +1100
Message-Id: <0CE3A534-C683-45C0-B7FA-4C1DDF942DA1@gmail.com>
To: Eric Carlson <eric.carlson@apple.com>
Cc: Philip J├Ągenstedt <philipj@opera.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Ah that works, too.

Sent from my iPhone

On 18/02/2010, at 3:04 PM, Eric Carlson <eric.carlson@apple.com> wrote:

> On Feb 17, 2010, at 4:06 PM, Silvia Pfeiffer wrote:
>> On Thu, Feb 18, 2010 at 1:53 AM, Eric Carlson  
>> <eric.carlson@apple.com> wrote:
>>>   I think "media" is only useful in markup. It allows the content  
>>> author to
>>> describe the characteristics of a resource, and it is used by the  
>>> UA to
>>> choose the most appropriate resource from a group of alternates  
>>> for a user's
>>> stated needs/preferences.  In other words, I don't think "media"  
>>> is an
>>> intrinsic property of the resource so we dont' need to expose it  
>>> in this API
>> Ah, so it basically inherits the @media attribute from the video
>> source. Would it maybe make sense, for reasons of exposing the same
>> API across internal and external tracks, to return the video source's
>> @media value in a track's media query if that attribute is read on an
>> internal track?
>   I am suggesting that we don't want a 'media' property in the API  
> at all, it is only useful in the markup.
> eric
Received on Thursday, 18 February 2010 05:39:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:09 UTC