This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16551 - Is there any reason for defaultUrl to be non-null in any but the first keymessage event?
Summary: Is there any reason for defaultUrl to be non-null in any but the first keymes...
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: David Dorwin
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-28 00:51 UTC by David Dorwin
Modified: 2012-08-17 06:28 UTC (History)
5 users (show)

See Also:

Attachments

Description David Dorwin 2012-03-28 00:51:18 UTC 
defaultUrl may be non-null when a keymessage event is fired from the generateKeyRequest() algorithm.

The only other case where a keymessage event might be fired is in step 5.6 of the addKey() algorithm. Is there a reason that a URL would need to be included in this event? Would it ever be different from the one in the event fired from the generateKeyRequest() algorithm or not known at that time?

v0.1 says defaultUrl will be NULL in the case that a keymessage event must be fired by the addKey() algorithm.
Comment 1 David Dorwin 2012-08-17 06:28:41 UTC 
defaultURL is now destinationURL in the object-oriented API (bug 16613), and there are cases where destinationURL may be set outside of generating a key request, such as a heartbeat message (bug 16738). Thus, I think this is obsolete.