- From: Mark Watson <watsonm@netflix.com>
- Date: Wed, 23 Mar 2011 18:46:09 -0700
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- CC: public-html <public-html@w3.org>
All, I think one thing which is missing from this proposal is an API to discover in-band tracks. A simple option would be to change the MediaElement.tracks array to list all kinds of track (audio/video/text and both those declared explicitly with markup and in-band ones). This can be queried to find the available tracks and new <audio> or <video> elements created for the ones that should be rendered, using a src with a media fragment to refer to in-band tracks. I'm happy to help update the proposal if people think this makes sense. ...Mark On Mar 21, 2011, at 10:34 PM, Silvia Pfeiffer wrote: > Dear WG chairs, > > Please find a change proposal for issue-152: multitrack media API here: > > http://www.w3.org/WAI/PF/HTML/wiki/Media_Multitrack_Change_Proposal > > Best Regards, > Silvia. > > > NOTE: > > This change proposal was created by a sub-group of the W3C Media > Accessibility Task Force. Many alternatives were looked at during the > process of creation of this change proposal (see [1]) and indeed not > all possibilities have been analysed to date. In fact, some of the > Task Force members are not in agreement with this proposal, which has > resulted in a second change proposal (see [2]). Further, several > members of the Task Force think that Ian's proposal (see [3]) is also > of high quality. It seems we just simply lack further discussion time > to arrive at a solution that everyone can agree to. > > [1] http://www.w3.org/WAI/PF/HTML/wiki/Media_Multitrack_Media_API > [2] http://www.w3.org/WAI/PF/HTML/wiki/Media_Multitrack_Change_Proposal_2 > [3] http://lists.w3.org/Archives/Public/public-html/2011Mar/0436.html > >
Received on Thursday, 24 March 2011 01:46:44 UTC