- From: <bugzilla@jessica.w3.org>
- Date: Wed, 28 Mar 2012 00:18:39 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16549 Summary: Remove initData parameter from addKey() Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Encrypted Media Extensions AssignedTo: adrianba@microsoft.com ReportedBy: ddorwin@google.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Depends on: 16548 This depends on the proposal in issue 16548 being accepted. If it is not accepted, then initData is required. >From v0.1: It has been proposed that the initData parameter, which would most likely contain inforamation identifying the key or keys needed, be removed from addKey() because any association can be done within the CDM using sessionId. (However, see Session Correlation <http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#issue-correlation>.) Such a change depends on requiring that generateKeyRequest() always be called before addKey(). Assuming that change is made, removing the parameter simplifies the API but hides all association between a key identifier and key. See this example <http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#issue-needkey-simple-event-example> for an illustration of the impact of this change. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 28 March 2012 00:18:41 UTC