[Bug 21854] Define MediaKeySession life cycle states and/or events

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

--- Comment #15 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to comment #14)
> So if the app wants to display a progress indicator, they will listen for
> needkey (which always happens) and then listen for keyready (which always
> happens)?

needkey fires on the media element. Then a session is created and then keyready
will eventually fire on the session (usually after keymessage/update
exchanges).

> If this is correct I don't understand the use case for the status attribute.
> It seems like the application knows exactly what the state is based on the
> messages it has seen.

Yes, you can determine the state by knowing what messages you've seen. We don't
have to expose the state but it is a low cost attribute assuming that generally
implementations will want to implement as a state machine of some kind and this
is a common pattern for APIs that have some kind of progress/state.

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

Received on Tuesday, 18 June 2013 21:19:48 UTC