Re: TextTrack API changes

On Thu, 25 Apr 2013 17:10:10 +0200, Bob Lund <B.Lund@cablelabs.com> wrote:

> There is getCueAsSource API in  
> http://www.w3.org/TR/2011/WD-html5-20110525/the-iframe-element.html#timed-text-tracks;  
> my mistake on the exact method name.

Please don't read /TR/, let alone a copy from 2011...

> The TextTrackCue text attribute as defined here  
> http://www.w3.org/TR/2012/CR-html5-20121217/embedded-content-0.html#text-track-api  
> is fine.

Again, /TR/ is obsolete.

See
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#texttrackcue
http://dev.w3.org/html5/webvtt/#dfn-webvttcue

> There is a definition for in-band MPEG-2 TS text tracks here  
> http://www.cablelabs.com/specifications/CL-SP-HTML5-MAP-I02-120510.pdf  
> that is normatively referenced by the DLNA HTML5 Remote UI spec. This  
> defines use of the TextTrackCue text and getCueAsHTML attributes.

Thanks. This seems to make use of .text, but not so much of  
getCueAsHTML(). The only thing that can return a non-null value for the  
latter is 5.2 Closed Captioning, which says

[[
getCueAsHTML() returns a DocumentFragment with an HTML representation of  
the TextTrackCue text attribute as defined in [HTML5], if the UA knows how  
to create such a representation. Otherwise, getCueAsHTML returns null.
]]

-- 
Simon Pieters
Opera Software

Received on Thursday, 25 April 2013 17:58:03 UTC