[Bug 20991] MediaKeys constructor failure case refers to unknown "new object".

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

--- Comment #2 from Mark Watson <watsonm@netflix.com> ---
I don't think we have events on MediaKeys yet, do we ?

With the current API, I think you have to assume that *both* MediaKeys and
MediaKeySession objects can exist whilst the underlying system is still
initializing.

Finally you will either get a keymessage or a keyerror on the *MediaKeySession*
(or presumably more than one of them if you have created more than one)

If we can define well enough what it means to have a MediaKeys object vs having
a MediaKeySession object then it might make sense to give te MediaKeys a
readyState and events to indicate when that changes (e.g. from INITIALIZING to
READY or INITIALIZING to ERROR). And then to require that the MediaKeys is in
READY state before you can call createSession().

What would be the meaning of a MediaKeys INITIALIZING state ? How would we
define that well enough that we don't end up with it being rather
browser-specific ?

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

Received on Monday, 1 April 2013 21:02:20 UTC