[Bug 24161] <track> short duration cues fail to reach the application

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

David Lewis <david.lewis4@bbc.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #2 from David Lewis <david.lewis4@bbc.co.uk> ---

I don't believe this response fully addresses the original bug.

I agree that a track where a cue has fallen between iterations of the time
marches on algorithm will become an affected track and therefore fire a
cuechange event. However at this point there is no sensible way to retrieve
that missed cue.

As an example consider the addition of the following attribute to the TextTrack
interface:

readonly attribute TextTrackCueList? missedCues;

This missedCues TextTrackCueList would contain the list created in step 4 of
the time marches on algorithm.

An application which is notified via the cuechange event may inspect the
activeCues list and find it empty. This would indicate a cue had ended or been
missed. Without maintaining a copy of the activeCues list at the time of the
previous cuechange, the cause is unclear. Inspecting the missedCues attribute
would indicate to the application that a cue had fallen in the gap. The
application could then access the data contained in the cue without having to
parse the full cues list for cues with a start and end time in the last 250ms.

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

Received on Wednesday, 22 January 2014 14:41:15 UTC