[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

--- Comment #2 from Qin Jiajia <jiajia.qin@intel.com> ---
(In reply to Aaron Colwell from comment #1)
> 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".
You are right if media element is going to transition to NETWORK_EMPTY. But, if
it changes to NETWORK_IDLE, what will happen to MediaSource? Does it still
work?

> 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."
Only transition to NETWORK_EMPTY will call "Detaching from a media element" or
NETWORK_EMPTY and NETWORK_IDLE both can call this algorithm?

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

Received on Tuesday, 18 November 2014 07:19:08 UTC