[Bug 18400] Define and document timestamp heuristics

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

--- Comment #9 from Aaron Colwell <acolwell@chromium.org> ---
Unless anyone objects, I'm just going to add step to the coded frame processing
algorithm
(https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html#sourcebuffer-coded-frame-processing)
that triggers an error if it encounters a segment that starts more than 100ms
from the 'last decode timestamp'.  

I think this should be sufficient to prevent developers from accidentally
creating large hidden holes in the content when they forget to call abort() for
an out-of-order append. It also allows a little bit of slop if the segment
start time doesn't exactly match with the previous segments end time.

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

Received on Thursday, 31 January 2013 18:11:45 UTC