14238 2011-09-22 09:09:47 +0000 <track> First argument of addTextTrack should be omissible, defaulting to subtitles 2012-09-14 12:13:51 +0000 1 1 1 Unclassified HTML.next default unspecified Other other RESOLVED LATER http://www.whatwg.org/specs/web-apps/current-work/#media-elements P3 normal --- 1 contributor dave.null eric.carlson ian mike plh public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 zcorpan public-html-bugzilla oldest_to_newest 57143 0 contributor 2011-09-22 09:09:47 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Multipage: http://www.whatwg.org/C#media-elements Complete: http://www.whatwg.org/c#media-elements Comment: First argument of addTextTrack should be omissible, defaulting to subtitles Posted from: 2001:4c28:a030:30:223:32ff:fec2:96fa by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.21 Safari/535.2 57746 1 ian 2011-10-04 01:09:13 +0000 Why? (And why "subtitles"? Surely "metadata" is more likely to be the common case?) 57757 2 zcorpan 2011-10-04 06:53:03 +0000 My thought was just that <track> has kind="" as optional and it defaults to subtitles, so i expected the api to do the same. 58600 3 ian 2011-10-20 23:34:45 +0000 The idea here is that <track> will almost always be used for subtitles, whereas the API will likely be used for metadata as much as anything else. I can make it default to "metadata" if you think that would be good, but I'm not sure it would. I don't have a strong opinion here. 58629 4 zcorpan 2011-10-21 08:19:01 +0000 We could start with having it required, and then in a few years see which kind is most common and revisit the issue.