[Bug 26372] Revisit the need for EME-specific DOMException names and the "error" attribute and event

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

Joe Steele <steele@adobe.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steele@adobe.com

--- Comment #3 from Joe Steele <steele@adobe.com> ---
Re: key availability -- 
I think cases 2, 3 and 5 will all result in the same action by the application
e.g. a new key request. 
I think case 1 will result in the same action, but is useful to keep separate
because it can tell the application the difference between never having
received a key and having received a bad key. 
I think cases 4 and 7 are unique, as the application may be able to do
something to allow playing but what will vary depending on the application. 
Case 6 is the hardest. I believe in most cases this means the content will
never be playable with the current configuration and an update to the UA/CDM is
required.  

Re: error reporting -- 
I don't like the general error attribute. It was useful before the Promises
changes were implemented, but now I think it makes more sense to have status
information per key (as you described) and then messaging when that status
changes.

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

Received on Monday, 21 July 2014 16:18:13 UTC