- From: <bugzilla@jessica.w3.org>
- Date: Mon, 25 Mar 2013 19:25:53 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21376
Aaron Colwell <acolwell@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acolwell@chromium.org
--- Comment #1 from Aaron Colwell <acolwell@chromium.org> ---
(In reply to comment #0)
> It is not clear why appending a coded frame whose decode timestamp is
> between the last decode timestamp and last decode timestamp + 100ms should
> trigger an error. What is the rationale for '100 ms' ?
Like the note states, this is to detect out of order appends. 100ms seemed like
a reasonable default that allows a little bit of flexibility on how far apart
coded frames are.
>
> Also, since the tests are made in decode order, maybe the Append Sequence
> definition should be clarified to say "monotonically increasing in *decode*
> time".
I'll add this in the next spec update.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 25 March 2013 19:25:55 UTC