[Bug 21431] Specify splicing behavior for text tracks

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21431

--- Comment #3 from Glenn Adams <glenn@skynav.com> ---
(In reply to comment #2)
> (In reply to comment #0)
> > 5. I believe multiple cues starting at the same timestamp are allowed in a
> > single text track. If so, should overlaps at that timestamp remove all the
> > cues at the timestamp or should there be special rules that allow targetting
> > individual cues?
> 
> What overlaps are you referring to? Such as: segment overlaps and the cues
> being delivered twice? IMHO, all we need to make sure is that cues have a
> unique identifier and when delivered twice don't get added to the list of
> TextTrackCues for rendering. The server then has to make sure to provide the
> same identifier for the same cue in any segmentation.

Keep in mind that a cue's identifier might be the empty string and if not an
empty string, does not need to be unique. So, it is permissible to have two
cues in a text track list that have an empty string as identifier and share the
same start and end times.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 29 March 2013 03:56:55 UTC