- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 31 Mar 2011 15:22:42 +1100
- To: Ian Hickson <ian@hixie.ch>
- Cc: Mark Watson <watsonm@netflix.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
On Thu, Mar 31, 2011 at 2:30 PM, Ian Hickson <ian@hixie.ch> wrote: > On Thu, 31 Mar 2011, Silvia Pfeiffer wrote: >> > >> > Video is harder since it involves assigning a playback region, so I >> > agree with the reasoning above for video tracks, more or less. But for >> > audio tracks it seems exposing them is fine. That's what both >> > Microsoft's proposal and the MediaController proposal do. >> >> Hmm are you suggesting to explicitly expose an audioTracks IDL >> attribute that has this information? It would be possible... > > What I'm proposing is: > > http://www.whatwg.org/specs/web-apps/current-work/complete.html#media-resources-with-multiple-media-tracks > > >> Incidentally, I don't quite buy into the ExclusiveTrackList / >> MultipleTrackList choice for audio and video tracks in the >> MediaController API. I think both video and audio tracks should be >> allowed to have multiple of them active at the same time. > > How do you propose that the user agent should render multiple video tracks > for a <video> element? My preferred option would be to render them into the video viewport next to each other (basically into inline css boxes inside the viewport box). But I am told, UAs render them simply over each other at the top left corner. In any case, there will be a default rendering IIUC. Silvia.
Received on Thursday, 31 March 2011 04:23:35 UTC