W3C home > Mailing lists > Public > public-webauthn@w3.org > November 2016

[webauthn] There is no "current settings object" in algorithm steps that are executing in parallel

From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
Date: Fri, 04 Nov 2016 17:58:06 +0000
To: public-webauthn@w3.org
Message-ID: <issues.opened-187399591-1478282285-sysbot+gh@w3.org>
bzbarsky has just created a new issue for 
https://github.com/w3c/webauthn:

== There is no "current settings object" in algorithm steps that are 
executing in parallel ==
https://w3c.github.io/webauthn/#dom-webauthentication-makecredential 
step 3 is using "current settings object's origin" in an algorithm 
step that is running async and hence no concept of "current settings 
object".  Note that async steps may also be running on separate 
execution threads, where settings objects, and origins, aren't even 
accessible.   Whatever work is done with settings objects and origins 
needs to be done before going async.

Please view or discuss this issue at 
https://github.com/w3c/webauthn/issues/254 using your GitHub account
Received on Friday, 4 November 2016 17:58:12 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:23 UTC