22329 2013-06-11 23:02:51 +0000 [MSE] TextTrack attributes settable in conflict with the html spec 2013-07-02 19:37:00 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC All RESOLVED WONTFIX P2 normal --- 1 giles adrianba acolwell kinetik mike public-html-media public-html-bugzilla oldest_to_newest 89137 0 giles 2013-06-11 23:02:51 +0000 "partial interface TextTrack { attribute DOMString kind; attribute DOMString language; }" The TextTrack interface in the html spec has readonly attributes of the same name. I think the idea is to use specific constructors as the only way to pass these in, or have them created by the parser for in-band text tracks and <track> elements. Do we need this interface? If it's muxed with the parent media element's source stream, the in-band text track support should cover it, and if it's external, the media.AddTextTrack and TextTrack.addCue methods should be sufficient to implement dynamic subtitles with minimal complexity. 89169 1 acolwell 2013-06-12 15:24:39 +0000 These attributes were intentionally made writable so that kind and language information that may be in the DASH manifest could be applied to specific tracks. Bug 17006 contains the initial discussion around this. The intent is to allow the application to override the information in the in-band tracks because it may either be wrong for the intended presentation or not even present. 90130 2 acolwell 2013-07-02 19:37:00 +0000 Resolving as WONTFIX base on discussion on the last media call (http://www.w3.org/2013/06/25-html-media-minutes.html). Please reopen with more information if my explanation was unacceptable.