[Bug 26313] Steps for createSession should define what happens if the sessionType is not supported

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

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ddorwin@google.com

--- Comment #1 from David Dorwin <ddorwin@google.com> ---
Step 4 currently says:
If sessionType is not supported by the content decryption module corresponding
to the keySystem, return a promise rejected with a new DOMException whose name
is "NotSupportedError".

I think that addresses this request. The only difference is that this happens
synchronously vs. asynchronously as would be the case in 7.4.x. I think this is
fine and consistent with other knowledge the UA must have about the CDM
(initDataType support, etc.).

I suppose there might be scenarios where support cannot be known a priori. A
CDM could always then report "NotSupportedError" in 7.7 in this scenario. I
think it's nice to do parameter verification together in the synchronous steps,
and this provides a quick and early escape for implementations that know they
do not support a specific session type. (I can see this being even more useful
if other session types are added.)

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

Received on Friday, 11 July 2014 21:50:53 UTC