Contact emailsnatiah...@google.com, a...@google.com

ExplainerNone

Specificationhttps://w3c.github.io/webauthn/#sctn-getClientCapabilities

Summary

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.


Blink componentBlink>WebAuthentication
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebAuthentication>

TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

None


*Gecko*: No signal

*WebKit*: Shipped/Shipping (
https://developer.apple.com/documentation/safari-release-notes/safari-17_4-release-notes#WebAuthn
)

*Web developers*: No signals

*Other signals*:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?

None


Debuggability

None


Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, ChromeOS, Android, and Android WebView)?Yes

Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
?Yes

https://wpt.fyi/results/webauthn/getclientcapabilities.https.html


DevTrial instructions
https://docs.google.com/document/d/e/2PACX-1vR3yUwIFZ0LbKpJ6J4GBamP-IrBgkal3arJ_CZLbRZwBDhFTZpdpVYMsPuvB6Mjnl0heE-6r9wE7Sfw/pub

Flag name on about://flagsenable-experimental-web-platform-features

Finch feature nameWebAuthenticationClientCapabilities

Requires code in //chrome?False

Tracking bughttps://g-issues.chromium.org/issues/360327828

Availability expectationSafari has shipped an implementation already.

Estimated milestones
Shipping on desktop 133
DevTrial on desktop 131
Shipping on Android 133
DevTrial on Android 131
Shipping on WebView 133

Anticipated spec changes

Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github issues
in the project for the feature specification) whose resolution may
introduce web compat/interop risk (e.g., changing to naming or structure of
the API in a non-backward-compatible way).
None

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5128205875544064?gate=5206408640069632

Links to previous Intent discussionsIntent to Prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/Wb8VjXe_zT8
Ready for Trial:
https://groups.google.com/a/chromium.org/g/blink-dev/c/YTkGIdlQMAw


This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 

Andrii Natiahlyi

Software Engineer

natiah...@google.com

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMrd0vy9wGn_fEQ4e9mX87cgz_jReJw7zOhbTrDweKARCUwyRw%40mail.gmail.com.

Reply via email to