PublicKeyCredential.getClientCapabilities - add

[hamishwillee]

FF135 adds support for PublicKeyCredential_getClientCapabilities().

This adds API reference.

Perhaps also an update to the guide.

#37557 is a precondition for this

Related docs work can be tracked in #37516

[github-actions]

Preview URLs

• /en-US/docs/Web/API/AuthenticatorAttestationResponse/getTransports
• /en-US/docs/Web/API/CredentialsContainer/get
• /en-US/docs/Web/API/PublicKeyCredential/getClientCapabilities_static
• /en-US/docs/Web/API/PublicKeyCredential
• /en-US/docs/Web/API/Web_Authentication_API

Flaws (3)

Note! 4 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/API/PublicKeyCredential/getClientCapabilities_static
Title: PublicKeyCredential: getClientCapabilities() static method
Flaw count: 3

• broken_links:
  • Can't resolve /en-US/docs/Web/API/PublicKeyCredential/signalAllAcceptedCredentials_static
  • Can't resolve /en-US/docs/Web/API/PublicKeyCredential/signalCurrentUserDetails_static
  • Can't resolve /en-US/docs/Web/API/PublicKeyCredential/signalUnknownCredential_static

External URLs (5)

URL: /en-US/docs/Web/API/CredentialsContainer/get
Title: CredentialsContainer: get() method

• https://web.dev/articles/passkey-form-autofill (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/API/PublicKeyCredential/getClientCapabilities_static
Title: PublicKeyCredential: getClientCapabilities() static method

• https://developers.google.com/identity/passkeys/developer-guides (1 time) (Note! This may be a new URL 👀)
• https://web.dev/articles/webauthn-related-origin-requests (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/API/AuthenticatorAttestationResponse/getTransports
Title: AuthenticatorAttestationResponse: getTransports() method

• https://en.wikipedia.org/wiki/Bluetooth_Low_Energy (1 time) (Note! This may be a new URL 👀)
• https://en.wikipedia.org/wiki/Near-field_communication (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2025-02-04 01:42:37)

[chrisdavidmills]

@hamishwillee nice work, sir. Few comments for you, but nothing really serious. I suspect you might change up a few things after reviewing my PR.

[chrisdavidmills]

"providing proof of possession of a credential private key provide" doesn't make sense; rephrase? Not sure if there is a missing word or something.

Also, the Chrome folks have a lot of detailed info about passkey. Maybe consider linking to something like https://developers.google.com/identity/passkeys/developer-guides?

[hamishwillee]

Yeah, that sux. What it was supposed to say is that you have to have a physical "thing" that grants access (which holds the credential's private key) and you require a user check to use it.

I've updated in https://github.com/mdn/content/pull/37734/files#r1936651860

It is still a little unclear to me if in reality all discoverable credentials are passkeys, and/or what differentiates a passkey from other discoverable credentials. Do you know?

[chrisdavidmills]

AIUI, passkeys are basically the main available use case for discoverable credentials right now, implemented by Google. Others may be available in the future, hence me saying "for example passkey" in my PR, to future proof the text.

[chrisdavidmills]

OK, that's fine.

[chrisdavidmills]

AIUI, passkeys are basically the main available use case for discoverable credentials right now, implemented by Google. Others may be available in the future, hence me saying "for example passkey" in my PR, to future proof the text.

[chrisdavidmills]

@hamishwillee few more bits for you, but nothing serious. I'm going to approve this, so as not to hold you up.

[hamishwillee]

@chrisdavidmills . I've accepted all your fixes (how was I so sloppy?) except the one about update/vs delete in the signal all credentials.

I'm going to merge because you'll be able to merge yours shortly too, and it would be good to fix the corresponding release note links to this.

Thanks very much for all your help and advice.