{"action":"closed","issue":{"url":"https://api.github.com/repos/w3c/encrypted-media/issues/22","labels_url":"https://api.github.com/repos/w3c/encrypted-media/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/w3c/encrypted-media/issues/22/comments","events_url":"https://api.github.com/repos/w3c/encrypted-media/issues/22/events","html_url":"https://github.com/w3c/encrypted-media/issues/22","id":55351358,"number":22,"title":"Request: Allow CDMs to support and enforce resolution restrictions (and expose the status of those restrictions to the application)","user":{"login":"ddorwin","id":9738764,"avatar_url":"https://avatars.githubusercontent.com/u/9738764?v=3","gravatar_id":"","url":"https://api.github.com/users/ddorwin","html_url":"https://github.com/ddorwin","followers_url":"https://api.github.com/users/ddorwin/followers","following_url":"https://api.github.com/users/ddorwin/following{/other_user}","gists_url":"https://api.github.com/users/ddorwin/gists{/gist_id}","starred_url":"https://api.github.com/users/ddorwin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ddorwin/subscriptions","organizations_url":"https://api.github.com/users/ddorwin/orgs","repos_url":"https://api.github.com/users/ddorwin/repos","events_url":"https://api.github.com/users/ddorwin/events{/privacy}","received_events_url":"https://api.github.com/users/ddorwin/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":30,"created_at":"2015-01-24T00:42:46Z","updated_at":"2015-08-25T15:05:34Z","closed_at":"2015-08-25T15:05:34Z","body":"\\[**March 6, 2015 Update**: The discussion has diverged from the original intent of this bug, including the text of this comment, and the first commit below. I have updated the title to reflect the discussion\\]\r\n\r\n[Bug 25409](https://www.w3.org/Bugs/Public/show_bug.cgi?id=25409) (\"Allow applications to detect whether a key is usable before using it to decrypt content\") explains the original motivation for the `keyStatuses` attribute and [Bug 25092 comment 33](https://www.w3.org/Bugs/Public/show_bug.cgi?id=25092#c33) explains the intended behavior and usage. However, this may not be clear from the spec text."}}