[Bug 11395] Use media queries to select appropriate <track> elements

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11395

--- Comment #6 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2010-12-04 01:21:43 UTC ---
(In reply to comment #5)
> Silvia: you're right, in that this is a slight extension of the 'display' to
> include the user's reception of the presented material, so it is a conceptual
> extension of media queries.
> 
> then, on "On top of this, there will be user settings in browsers for the
> preferred
> tracks to be active by default. If the kind/lang combination of a track matches
> a user's preferences, the track will automatically be turned on." -- we have a
> system that delivers an on/off signal, and it's called media queries.  Rather
> than inventing a new 'type' indicator, which is what we're doing, I'd like to
> explore using the existing one.


It's not really a new system - browser preference language settings already
influence what we see on the Web. The @kind attribute just adds the type of
accessibility content to this existing feature.


> Particularly, this (a) allows the rest of the page to respond as well (so,
> trivially, I could show something that confirms I see your preference "captions
> enabled") and (b) if we can 'style' the tracks in the video element as well as
> the element itself, then (perhaps) the layout of that element and the rest of
> the page can change (allowing by-side captioning rather than overlay, if
> desired, for example).
> 
> that was my broad vision, anyway...

I'm curious what you mean by "the rest of the page responds" and "style the
tracks". Are you talking about exposing the state to JavaScript, such that a
JavaScript developer can then grab the captions in display them side-by-side
rather than as overlay as they are displayed by default? Can you give a
concrete example where the @media query works but the @kind/@lang attribute
doesn't?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 4 December 2010 01:21:46 UTC