16551 2012-03-28 00:51:18 +0000 Is there any reason for defaultUrl to be non-null in any but the first keymessage event? 2012-08-17 06:28:41 +0000 1 1 1 Unclassified HTML WG Encrypted Media Extensions unspecified All All RESOLVED INVALID P3 normal --- 1 ddorwin ddorwin eric.carlson mike philipj public-html-media public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 66170 0 ddorwin 2012-03-28 00:51:18 +0000 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. 72338 1 ddorwin 2012-08-17 06:28:41 +0000 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.