[Bug 18515] Provide more details on behavior of the media element when the key for an encrypted block is not available

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

--- Comment #11 from David Dorwin <ddorwin@google.com> ---
(In reply to comment #10)
> I agree with the proposal to just follow what the HTMLMediaElement spec says
> should happen if readyState is not HAVE_FUTURE_DATA or HAVE_ENOUGH_DATA.
> 
> But I am not sure that fully answers the questions I raised. Does this mean
> the media element remains in the HAVE_FUTURE_DATA state forever? Or can the
> CDM signal that it has determined that the proper key will never be acquired
> and therefore playback should be stopped and an error reported?

The proposal in Comment 7 was to behave the same as specified when readyState
is not HAVE_FUTURE_DATA or HAVE_ENOUGH_DATA. It didn't actually mean that
readyState would change.

Comment 8 further adds that we may actually want/need to change readyState. We
might define "data" as unencrypted data and say that the element does not have
data unless it is/can be decrypted.

Any CDM signal or error would be reported via a MediaKeyError on a
MediaKeySession. This would indicate a failure in the session, but it does not
affect the state of the element (i.e. it could be resumed by providing the key
in another session).

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

Received on Thursday, 1 August 2013 22:54:46 UTC