W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2010

[whatwg] ambiguity in timed tracks API part of spec?

From: Bruce Lawson <brucel@opera.com>
Date: Fri, 05 Nov 2010 09:29:00 -0000
Message-ID: <op.vloxymw9h8on37@bruce-pc>
http://www.whatwg.org/specs/web-apps/current-work/complete/video.html#sourcing-in-band-timed-tracks
says to create TimedTrack objects etc for in-band tracks which are then  
exposed in the API - so captions/ subtitles etc that are contained in the  
media container file are exposed, as well as those tracks pointed to by  
the <track> element.

But  
http://www.whatwg.org/specs/web-apps/current-work/complete/video.html#timed-track-api  
implies that the array is only of tracks in the track element:

"media . tracks . length

Returns the number of timed tracks associated with the media element  
(e.g.  from track elements). This is the number of timed tracks in the  
media element's list of timed tracks."

Suggestion: amend to say "Returns the number of timed tracks associated  
with the media element (e.g.  from track elements and any in-band track  
files inside the media container file)" or some such.

Hang loose and stay groovy,

Bruce Lawson
Web Evangelist
www.opera.com (work)
www.brucelawson.co.uk (personal)
www.twitter.com/brucel
Buy my HTML5 book www.introducinghtml5.com
Received on Friday, 5 November 2010 02:29:00 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC