Technical review: Add WebAuthn Signal API #37557
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Chrome 132 supports the WebAuthn Signal API. Specifically, this means support for the following static methods:
PublicKeyCredential.signalAllAcceptedCredentials()
PublicKeyCredential.signalCurrentUserDetails()
PublicKeyCredential.signalUnknownCredential()
This PR adds reference pages for all of the above methods. It also attempts to consolidate all the information on MDN about discoverable credentials into a single section on the WebAuthn home page. I noticed that quite a few details were dotted around on various pages, and wanted to link all of the reference pages I added to a single place for more information, rather than having to explain discoverable credentials on each page.
Please let me know if this writeup of discoverable credentials sounds correct.
Motivation
Additional details
Related issues and pull requests