- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 19 Feb 2010 16:56:10 +1100
- To: Eric Carlson <eric.carlson@apple.com>
- Cc: David Singer <singer@apple.com>, philipj@opera.com, Geoff Freed <geoff_freed@wgbh.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Fri, Feb 19, 2010 at 4:49 PM, Eric Carlson <eric.carlson@apple.com> wrote:
>
> On Feb 18, 2010, at 3:24 PM, David Singer wrote:
>
>>
>> It seems to be that if a trackgroup represents an optional feature (e.g. "captions"), then
>>
>> a) the expression that says whether the trackgroup as a whole is wanted or not, should be, well, at the trackgroup level (a media query)
>> b) *which* of the trackgroup you want should be expressed by attributes on the enclosed tracks.
>>
>> Do we need something at the trackgroup level that gives me a clue what criteria to use to select between the tracks? ("These differ by language", "These differ by mime type") or do we have a rule that is like <source> ... walk down the group and enable the first that seems supportable (and implicitly disable the rest)? I am kinda not keen on 'best match' specifications (but they are hard to avoid when talking about languages).
>>
> I am in favor of using the same model we have with <source> - the content author "describes" each alternate with attributes and the UA picks the first one that is appropriate for the user's preferences and machine environment.
I agree. I think it's basically what I have described here:
http://www.w3.org/WAI/PF/HTML/wiki/Media_TextAssociations#Resource_selection_algorithm
. Let me know if that captures it.
Cheers,
Silvia.
Received on Friday, 19 February 2010 05:57:05 UTC