- From: <bugzilla@jessica.w3.org>
- Date: Fri, 25 Jul 2014 23:52:26 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26401 --- Comment #1 from David Dorwin <ddorwin@google.com> --- (In reply to Joe Steele from comment #0) > The usage of destinationURL has been removed from section 8.2. "Selecting a > Supported Key System and Using Initialization Data from the 'needkey' > Event". This should be added back in to let application implementors know > that it is required for some CDMs. I don't think destinationURL was ever in the examples. As discussed in the telecon, your use case is unclear. The "needkey" event interface [1] has never had a URL. destinationURL has always only been in the "message" event interface [2]. The Queue a "message" Event algorithm [3] defines the creation of [2]. It may be called in four cases: 1) createSession() algorithm (destinationURL is null) 2) loadSession() algorithm 3) update() algorithm 4) Other times the CDM needs to send a message, such as to request renewal. The example in 8.2 is a simple one that assumes the "message" event is a license request, which it handles in licenseRequestReady(). This is case #1. [1] https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html#dom-mediakeyneededevent [2] https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html#dom-mediakeymessageevent [3] https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html#algorithms-queue-message -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 25 July 2014 23:52:28 UTC