This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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
Why? (And why "subtitles"? Surely "metadata" is more likely to be the common case?)
My thought was just that <track> has kind="" as optional and it defaults to subtitles, so i expected the api to do the same.
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.
We could start with having it required, and then in a few years see which kind is most common and revisit the issue.