[Bug 27342] Clarify if the source buffer is still valid when appendBuffer/appendStream meets 'decode' error

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

Aaron Colwell <acolwell@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |acolwell@google.com
           Assignee|adrianba@microsoft.com      |acolwell@google.com
   Target Milestone|---                         |CR

--- Comment #1 from Aaron Colwell <acolwell@google.com> ---
If you look at the "If the media data is corrupted" step in the HTML5 spec
(http://www.w3.org/TR/html5/embedded-content-0.html#fatal-decode-error) you
will see that there is a step that causes networkState to get set to
NETWORK_EMPTY. This causes the "Detaching from a media element" algorithm
(https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html#mediasource-detach)
to run. That is why there is a transition to "closed".

Based on this, I don't believe there is a conflict in the MSE spec. A compliant
implementation should transition readyState to "ended" as a result of running
the end of stream algorithm, and then transition readyState to "closed" as a
result of the detaching from a media element algorithm being run because
networkState got transitioned to NETWORK_EMPTY.

I can add a note under the "Run the media data is corrupt steps of the resource
fetch algorithm." saying something like "This step can cause the 'detaching
from a media element algorithm' to run."

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

Received on Monday, 17 November 2014 17:31:31 UTC