Re: [me-media-timed-events] event is not defined (#41)

> My issue was addressing the browser interoperability issue

@mavgit Ah I see, then the question is not "should zero duration cues appear in the active cue list?" but "what is the minimum duration of a cue to guarantee that it appears in the active cue list?", and the answer to that is almost certainly 250ms right now. Bringing down the synchronisation threshold to 20ms as proposed would presumably reduce it to 20ms.

But there's a bigger question, which is: what use case depends on cues being added to the active cue list reliably? If this reliability is a dependency for some code, it either needs to set the duration to be long enough, or be refactored to remove the dependency, by using cue events rather than text track cue list events.

-- 
GitHub Notification of comment by nigelmegitt
Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/41#issuecomment-488607318 using your GitHub account

Received on Thursday, 2 May 2019 09:22:37 UTC