[Bug 16548] Require generateKeyRequest() in all cases for all Key Systems

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16548

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |17203, 16550

--- Comment #6 from David Dorwin <ddorwin@google.com> 2012-06-19 18:58:18 UTC ---
One option is that the user agent should fire an INVALID_STATE_ERR if addKey()
or cancelKeyRequest() are called before an appropriate (i.e. same keySystem)
successful call to generateKeyRequest().

However, should we also require a valid session ID (bug 17203), which would
also require that generateKeyRequest() had been called? Note that the current
draft says to throw an INVALID_ACCESS_ERR if sessionId is unrecognized.
However, that assumes the session ID check is synchronous, which may not make
sense (bug 16550).

This discussion may be moot depending on the specific solution to bug 16613.

-- 
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 Tuesday, 19 June 2012 18:58:21 UTC