[Bug 18400] Define and document timestamp heuristics

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

--- Comment #8 from Aaron Colwell <acolwell@chromium.org> ---
Since out-of-order appends require an abort() call now, I believe this isn't as
big of a problem anymore. With the current spec text, appending data that is
before the last data appended w/o an intervening abort() will trigger an error.
Appending data far beyond the last data won't generate an error, but will
likely lead to a bad user experience. 

Should we still add a heuristic that requires media segments to be within 2
frame intervals of eachother to avoid developers from accidentally creating
large gaps in the media when they forget to call abort()?

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

Received on Friday, 28 December 2012 21:47:31 UTC