W3C home > Mailing lists > Public > public-html@w3.org > March 2012

[Bug 16551] New: Is there any reason for defaultUrl to be non-null in any but the first keymessage event?

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Mar 2012 00:51:21 +0000
To: public-html@w3.org
Message-ID: <bug-16551-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16551

           Summary: Is there any reason for defaultUrl to be non-null in
                    any but the first keymessage event?
           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


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 28 March 2012 02:17:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:31 UTC