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

[bzbarsky]

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.

[bzbarsky]

This applies to https://w3c.github.io/webauthn/#getAssertion step 3 too.

[equalsJeffH]

(finally) assigned myself to this one since I've been planning to work on this - in part because our (inappropriate) use of current settings object is my doing :)

I attempted to also assign @jyasskin, but he is not showing up in the pick list for assignees.

[jyasskin]

I'm in the w3c organization, but maybe I need to be on a team with explicit 'read' access to this repository in order to be assigned issues. See the blue box on https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/.