[Bug 21276] Some instances of throwing append error should call endOfStream

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

Aaron Colwell <acolwell@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|adrianba@microsoft.com      |acolwell@chromium.org

--- Comment #3 from Aaron Colwell <acolwell@chromium.org> ---
(In reply to comment #2)
> The problem is that you don't know what state the buffer is in after a
> partial append. If we don't halt at this point then we need to somehow get
> the buffer into a "known good" state.

I figured that this was roughly equivalent to abort() being called since the
"reset parser state algorithm" is run to put the parser into a known state. The
application can look at the buffered attribute to assess what likely got
successfully appended in the buffer. It can then choose to retry the append or
it could select a different media segment to cover the unbuffered range that
would have been covered by the failed append.

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

Received on Wednesday, 20 March 2013 15:02:48 UTC