Steps to reproduce:

Try to use PublicKeyCredential.parseCreationOptionsFromJSON(…) or PublicKeyCredential.parseRequestOptionsFromJSON(…).

From the spec:
https://w3c.github.io/webauthn/#sctn-parseCreationOptionsFromJSON
https://w3c.github.io/webauthn/#sctn-parseRequestOptionsFromJSON

Expected results:

It would be really useful to see these methods implemented, as basically every site using WebAuthn has to deserialize requests and serializes responses for the server.

Right now, I maintain a library ^1 that implements this functionality, but it's tricky to keep up with the spec and browser compatibilities over time.

The API methods work for RPs out of the box, with no additional client code, and are much more future-proof. It would be very beneficial for the ecosystem for these to be available in browsers sooner rather than later, so that sites and WebAuthn implementation guides don't hardcode forwards-incompatible assumptions.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Web Authentication' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.