[Bug 21079] addTextTrack() incorrectly assumes WebVTT content type

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

--- Comment #2 from Glenn Adams <glenn@skynav.com> ---
(In reply to comment #1)
> Even though we are still discussing how to resolve bug 21851 properly, I
> think we can already apply the patch to this part of the spec from HTML5.1.
> 
> I suggest we change:
> 
> "Associate the text track list of cues with the rules for updating the
> display of WebVTT text tracks as its rules for updating the text track
> rendering. [WEBVTT]"
> 
> to
> 
> "Initially, the text track list of cues is not associated with any rules for
> updating the text track rendering. When a text track cue is added to it, the
> text track list of cues has its rules permanently set accordingly."
> 
> And in the addCue [1] description we change:
> 
> "1. If the given cue is in a text track list of cues, then remove cue from
> that text track list of cues.
> 
> 2. Add cue to the method's TextTrack object's text track's text track list
> of cues."
> 
> to
> 
> "1. If the text track list of cues does not yet have any associated rules
> for updating the text track rendering, then associate the text track list of
> cues with the rules for updating the text track rendering appropriate to cue.
> 
> 2. If text track list of cues' associated rules for updating the text track
> rendering are not the same rules for updating the text track rendering as
> appropriate for cue, then throw an InvalidStateError exception and abort
> these steps.
> 
> 3. If the given cue is in a text track list of cues, then remove cue from
> that text track list of cues.
> 
> 4. Add cue to the method's TextTrack object's text track's text track list
> of cues.
> "
> 
> [1] http://www.w3.org/TR/html5/single-page.html#dom-texttrack-addcue

I believe this will work, though it does mean that the cues associated with a
text track must all share the same associated rules, meaning further that, if a
text track content type, like text/vtt supports multiple cues (of different
associated rules), then the cues of that track content type must be effectively
demuxed into distinct track cue lists. Is that your intention?

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

Received on Monday, 13 May 2013 06:41:53 UTC