Re: TextTrack API changes

On Thu, Apr 25, 2013 at 8:46 AM, Glenn Adams <> wrote:

> On Wed, Apr 24, 2013 at 3:23 PM, Silvia Pfeiffer <
>> wrote:
>> Firstly note that there never was a getCueAsText() API. If mpeg2 requires
>> one, then that would be specific to a Mpeg2Cue API and I recommend against
>> adding it to TextTrackCue.
> That was just a typo.

Ah ok - it was repeated by several people so I thought it was for real.

>  I'm prepared to add the .text and getCueAsHTML() interfaces to
>> TextTrackCue if there is a definition of another XXXCue interface that has
>> these. For example SCCTrackCue could define these, assuming the track was a
>> 708 track and converted to SCC.
> Since these were already defined on TextTrackCue without explicit
> definition of their use with another format, and the language explicitly
> abstracted this fact, then it is not required to define any other mapping
> in HTML5.

That is not quite true. TextTrackCue was only "real" with a defined
mapping. FAIK the only defined mapping that existed was the WebVTT mapping.
Can you link me to another one that actually is using TextTrackCue? Where
is the MPEG4 one defined? Which browser exposes it with TextTrackCue?


Received on Friday, 26 April 2013 00:53:15 UTC