mdn/content

WebAuthn conditional create is not documented

Open

#42,516 建立於 2025年12月24日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Markdown (8,900 star) (22,427 fork)batch import
Content:WebAPIarea: WebAuthndocument not writtenhelp wanted

描述

https://github.com/w3c/webappsec-credential-management/pull/224 added a mediation option to CredentialsContainer.create(), to enable websites to support conditional create, AKA automatic passkey creation.

This should be documented on MDN.

In fact it would be good to rework https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API#discoverable_credentials_and_conditional_mediation, to make it clear that it's really about autofill (and to downplay the stuff about discoverable credentials), and move it into a separate guide page that also covered conditional create.

貢獻者指南

技術棧
javascript
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
WebAuthn API basicsMDN contribution guide
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
The issue requests documenting the `mediation` option for `CredentialsContainer.create()` as part of WebAuthn conditional create. The MDN page at https://developer.mozilla.org/en US/docs/Web/API/Web Authentication API#discoverable credentials and conditional mediation should be reworked to focus on autofill and moved to a separate guide page. A separate guide covering conditional create using the specification (w3c/webappsec credential management#224) and Chrome's developer documentation should be created. No existing pull requests or comments are present, so work can start fresh.