Major unresolved issues with or opposition to this design:
There has been no voiced opposition to the addition of this feature. There is active discussion about the nature of the UI that will be shown by browsers when this is invoked. Specs are not typically prescriptive about UI but we consider it important that there be some consistency across major browsers.
You should also know that...
The Security and Privacy questionnaire is not linked in the explainer but one exists.
The PR was discussed during the WebAuthn WG session at TPAC in October 2027 and there was broad support but TAG review is requested before it can be merged.
<!-- Content below this is maintained by @w3c-tag-bot -->
OpenedOct 9, 2026
Explainer
https://github.com/w3c/webauthn/blob/main/explainers/conditional-ui-without-autofill.md
The explainer
Where and by whom is the work is being done?
GitHub repo: https://github.com/w3c/webauthn
Primary contacts:
Organization/project driving the design: Google Chrome
Incubation and standards groups that have discussed the design:
Standards group(s) that you expect to discuss and/or adopt this work when it's ready: None
Feedback so far
Multi-stakeholder feedback:
Major unresolved issues with or opposition to this design: There has been no voiced opposition to the addition of this feature. There is active discussion about the nature of the UI that will be shown by browsers when this is invoked. Specs are not typically prescriptive about UI but we consider it important that there be some consistency across major browsers.
You should also know that...
The Security and Privacy questionnaire is not linked in the explainer but one exists.
Draft PR: https://github.com/w3c/webauthn/pull/2485
The PR was discussed during the WebAuthn WG session at TPAC in October 2027 and there was broad support but TAG review is requested before it can be merged.
<!-- Content below this is maintained by @w3c-tag-bot -->Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1291