[Bug 24025] Add optional configuration parameter to MediaKeys constructor

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

Joe Steele <steele@adobe.com> changed:

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

--- Comment #8 from Joe Steele <steele@adobe.com> ---
(In reply to David Dorwin from comment #6)
> If one or more of the items in the dictionary is unrecognized or unsupported
> by the CDM, what should happen?
> 
> 1. Report a MediaKeyError (NOT_SUPPORTED_ERR or INVALID_ACCESS_ERR).
> 2. Throw an exception.
>  * This is probably more app-friendly than #1, but it requires the UA to
> know acceptable values, some of which could require probing. Thus, I don't
> think it is an option.
> 3. Ignore such values.
>  * For recognized but unsupported values, do the best possible.
>  * The server decide whether it's sufficient.
>  * This potentially allows a single dictionary to be passed to all CDMs.
> 4. Ignore unrecognized values but let the CDM report errors for recognized
> but unsupported values if appropriate.
>  * This seems to add too much ambiguity.

I vote for option #3 here. But I would say we need a little more clarity. 

Is a CDM free to ignore a single value or set of values? Or if an unknown value
is present, must it ignore the entire dictionary? I would vote for the former
as it is more flexible. 

I am fairly agnostic as to whether the parameter is a dictionary or a JSON
string. However I will point out that if this is a JSON string, the CDM will be
forced to include a parser it does not have today and that could be a source of
errors.

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

Received on Tuesday, 18 February 2014 08:13:04 UTC