[encrypted-media] Clarify behavior for denied user consent

ddorwin has just created a new issue for 
https://github.com/w3c/encrypted-media:

== Clarify behavior for denied user consent ==
Step 15 of the _Get Supported Configuration_ algorithm defines when to
 prompt for use of Distinctive Identifier(s). (Issue #51 is related to
 cleaning this up.) However, it does not say what to do when such 
consent is denied.

The simple solution is to return null as in step 14.

However, it's possible that the configuration could have been 
supported in a different way^. We may want to allow reprocessing of 
the _candidate configuration_ (plus changes based on the denied 
consent).

We might also want to generalize the text, while still emphasizing the
 importance for Distinctive Identifiers, to cover checking consent for
 other reasons (beyond the existing note).

^ For example, if _candidate configuration_'s `distinctiveIdentifier` 
value is `"optional"`, knowing that the consent is denied might have 
allowed selection of a different set of `videoCapabilities` that don't
 require a Distinctive Identifier).

See https://github.com/w3c/encrypted-media/issues/57

Received on Monday, 18 May 2015 23:55:48 UTC