- From: Ken Buchanan via GitHub <noreply@w3.org>
- Date: Wed, 03 Dec 2025 22:29:01 +0000
- To: public-webauthn@w3.org
@rmondello > I can see how the shape of what I’m proposing for “immediate” and the ambient proposal are isomorphic, but since the intended use case and behavior in the UA are so different, they’re different, right? One key difference between the Immediate and Ambient proposals is that Immediate requires a user activation and Ambient does not. You are suggesting that we modify Immediate so that it does not return if there are no credentials. In that case the user would click "Sign In", the site would (frequently) navigate to its sign-in page (e.g. example.com -> login.example.com), and then invoke the call to show the more prominent passkey UI. Would this keep the user activation requirement? If yes then that wouldn't really work, because the user would have to take some action on the sign-in page before the UI could appear, which seems to largely defeat the purpose. If no then pages could open this UI immediately when the user lands on their home page, which I suspect we agree would be undesirable for a modal dialog. Is this something that has been considered on your side? -- GitHub Notification of comment by kenrb Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2228#issuecomment-3609117332 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 December 2025 22:29:01 UTC