-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementing a time out for fallback UX #254
Comments
Perhaps obvious since I'm already quoted in the OP, but I think this is a good idea (assuming folks need timeout support) :D. cc @nickburris to put this on your radar |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A developer has told me that it would be useful to close the fallback UX after a timeout rather than leave it open indefinitely (e.g., if the UX has created confusion and the user simply leaves the window).
@stephenmcgruer pointed out that WebAuthn encourages [1] developers to leverage the DOM specification's AbortController interface [2] and thought we might be able to do the same thing for this use case.
[1] https://www.w3.org/TR/webauthn-2/#sctn-abortoperation
[2] https://dom.spec.whatwg.org/#abortcontroller
The text was updated successfully, but these errors were encountered: