FYI - Web Authentication API: PublicKeyCredential’s getClientCapabilities() method

[natiahlyi]

こんにちは TAG-さん!

Per the Chromium Intent to Ship, it was advised that I file a TAG review as a FYI, because this is related to feature detection - hence this request.

I'm requesting a TAG review of Web Authentication API: PublicKeyCredential’s getClientCapabilities() method.

getClientCapabilities() method allows to determine which WebAuthn features are supported by the user's client. The method returns a list of supported capabilities, allowing developers to tailor authentication experiences and workflows based on the client's specific functionality. Context: w3c/webauthn#1923

• Explainer¹: none
• Specification: https://w3c.github.io/webauthn/#sctn-getClientCapabilities
• WPT Tests: https://wpt.fyi/results/webauthn/getclientcapabilities.https.html
• User research: none
• Security and Privacy self-review²:
• GitHub repo: https://github.com/w3c/webauthn/
• Primary contacts:
  • Andrii Natiahlyi (@natiahlyi), Google, implementing the feature in Chromium
• Organization/project driving the specification: the WebAuthn Working Group
• Multi-stakeholder support³:
  • Chromium comments: yes
  • Mozilla comments: Web Authentication API: PublicKeyCredential’s getClientCapabilities() method mozilla/standards-positions#1114
  • WebKit comments: Added support for getClientCapabilities(). (119058559)
• Status/issue trackers for implementations⁴: https://chromestatus.com/feature/5141695044255744?gate=5532327385497600

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines:
• The group where the work on this specification is currently being done: WebAuthn WG
• Major unresolved issues with or opposition to this specification: None
• This work is being funded by: Google

[torgo]

As discussed on today's call.