Re: Removing cues with duplicate ids as a way to allow cue rewriting

On 05/28/2014 08:28 AM, Philip Jägenstedt wrote:
> On Tue, May 27, 2014 at 5:01 PM, Brendan Long <self@brendanlong.com> wrote:
>> On 05/26/2014 04:18 AM, Philip Jägenstedt wrote:
>>
>> TextTrackCue.id is mutable, so that setter would have to throw (or
>> something) to guarantee that there are no duplicate ids. Elements have
>> non-unique ids and getElementById() can still be implemented efficiently, so
>> I disagree that a non-unique TextTrackCue.id is a problem worth solving in
>> its own right.
>>
>> That makes sense. It probably isn't worth handling at the HTML level. Doing
>> this in the WebVTT parser would work though.
> Can you file a WebVTT bug for live streaming with corrections? If one
> treats the corrected cue like a new cue, maybe it can be solved in the
> same way as cues with initially unknown end times that can at any time
> be replaced by a new cue. (No solution exists for that either, yet.)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25910

Received on Wednesday, 28 May 2014 14:00:43 UTC