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

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