- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 17 May 2013 12:12:54 +1000
- To: Pierre-Anthony Lemieux <pal@sandflow.com>
- Cc: Michael Jordan <mijordan@adobe.com>, "public-tt@w3.org" <public-tt@w3.org>
On Fri, May 17, 2013 at 12:03 PM, Pierre-Anthony Lemieux <pal@sandflow.com> wrote: >> Because most browsers have refused to implement TTML support in the past. > > But browsers intend to implement the TextTrackAPI, and the > TextTrackAPI is read-write, i.e. one can both read and create cues, > right? Yes... but that is unrelated to having TTML support in the browser. What TTML in the browser means is that there is a specification for TTMLCue() (such that cues get exposed to the browser and a JS interface is available), and that a browser has decided to parse TTML files int a TextTrack and create TTMLCues from that file. The first half is part of the charter. The second half requires browsers to decide to implement TTML support. IE10 is the only browser this far that has decided to implement TTML file parsing, but it has not implemented a JS API for TTML content. HTH. Regards, Silvia.
Received on Friday, 17 May 2013 02:13:42 UTC