- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Jul 2012 23:05:34 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17658
Mark Watson <watsonm@netflix.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |watsonm@netflix.com
--- Comment #1 from Mark Watson <watsonm@netflix.com> 2012-07-03 23:05:34 UTC ---
The key system is selected with the call to generateKeyRequest(). If that
keysystem is not supported (by the browser, or by the file) then the call will
fail and the app can try a different keysystem.
Note that all three of the app, the file and the browser may support multiple
keysystems. Only a keysystem in the intersection of these three sets may be
used. There may still be more than one. The app needs to choose its favorite
from that set, as there may be commercial implications of the choice for the
app.
The way we chose to implement that was by allowing the app to attempt
generateKeyRequest with different key systems, in preference order, until one
succeeded.
That seems acceptable given that the set of keysystems in the intersection I
describe above is likely to be very small (coming up with an example where
there are 3, say, is already a challenge).
--
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, 3 July 2012 23:05:36 UTC