- From: <bugzilla@jessica.w3.org>
- Date: Tue, 11 Jun 2013 23:02:51 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22329 Bug ID: 22329 Summary: [MSE] TextTrack attributes settable in conflict with the html spec Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions Assignee: adrianba@microsoft.com Reporter: giles@mozilla.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org "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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 11 June 2013 23:02:56 UTC