W3C home > Mailing lists > Public > public-html@w3.org > May 2013

Re: TextTrack API changes

From: Simon Pieters <simonp@opera.com>
Date: Tue, 07 May 2013 09:41:21 +0200
To: "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>
Cc: "Bob Lund" <B.Lund@cablelabs.com>, "Glenn Adams" <glenn@skynav.com>, public-html <public-html@w3.org>, "Jerry Smith, (WINDOWS)" <jdsmith@microsoft.com>, "Mark Vickers @ Comcast" <mark_vickers@cable.comcast.com>
Message-ID: <op.wwpea7cqidj3kv@simons-macbook-pro.local>
On Mon, 06 May 2013 15:42:16 +0200, Silvia Pfeiffer  
<silviapfeiffer1@gmail.com> wrote:

>> This is false. It was only possible to create WebVTT cues with the
>> TextTrackCue() constructor. (This is an argument against reintroducing  
>> it.)
>>
>
>
> You can try on Chrome. Just do cue = new TextTrackCue(0,5,"test"); It
> works. Doesn't need to be anything specific.

Chrome implements the old spec where TextTrackCue() creates a WebVTT cue.  
The "test" above is parsed using WebVTT parsing rules. The created cue has  
WebVTT-specific properties.

But if you mean by

[[
previously it was possible to construct a cue of any type and append it to  
a track with interpretation of cue content done by JavaScript
]]

that it was possible to construct a WebVTT cue with cue content of a  
different format and interpret the cue content with JavaScript, then that  
is still possible with new WebVTTCue().

-- 
Simon Pieters
Opera Software
Received on Tuesday, 7 May 2013 07:42:04 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:02 UTC