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

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

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |watsonm@netflix.com

--- Comment #1 from David Dorwin <ddorwin@google.com> ---
The CDM load failure path assumes that the object has been created. I also note
that CDM loading is synchronous, which may not be a good idea.

How should we handle load failures?

If loading is synchronous, the only thing we can do is throw an exception and
not create the MediaKeys.

If loading is asynchronous, we'd return an un-/partially-initialized MediaKeys
object and fire a keyerror at it. This gives us the most flexibility in
reporting specific error codes, but I worry about having a MediaKeys that is
not fully initialized and no event to say it is initialized. For example, what
happens in the (likely) case that the app immediately calls createSession() on
the new object? Do we just post a task to handle this once the CDM is ready?

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

Received on Monday, 1 April 2013 20:39:46 UTC