Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove vestigial reference to CollectedClientData/clientExtensions #835

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -3743,9 +3743,8 @@ Note: Extensions should aim to define authenticator arguments that are as small
## <dfn>Client extension processing</dfn> ## {#sctn-client-extension-processing}

Extensions MAY define additional processing requirements on the client platform during the creation of credentials or the
generation of an assertion. The [=client extension input=] for the extension is used an input to this client processing.
Supported [=client extensions=] are recorded as a dictionary in the [=client data=] with the key
{{CollectedClientData/clientExtensions}}. For each such extension, the client adds an entry to this dictionary with the
generation of an assertion. The [=client extension input=] for the extension is used as an input to this client processing.
For each supported [=client extension=], the client adds an entry to the |clientExtensions| [=map=] with the
[=extension identifier=] as the key, and the extension's [=client extension input=] as the value.

Likewise, the [=client extension outputs=] are represented as a dictionary in the result of {{PublicKeyCredential/getClientExtensionResults()}}
Expand Down