I would like if startAuthentication would support "Immediate UI" (uiMode: immediate). Here are some explainers:
Proposal 1
Add a new option to startAuthentication (for example useImmediateUIMode) that configures the options passed to navigator.credentials.get for Immediate UI (like I did in #779). As there is still some movement about this API and only Chrome implements it yet, there might be breaking changes to this API in the future.
Proposal 2
Add a new getOptions: Partial<CredentialRequestOptions> option that is spread into the options passed to navigator.credentials.get or maybe even better a callback modifyOptions: (options: CredentialRequestOptions) => CredentialRequestOptions (there is 100% a better name for both of these 😅). This way users are free to use options not supported by startAuthentication and are responsible for dealing with breaking changes.
Once Immediate UI is more stable it can still be added as a supported option.
I would like if
startAuthenticationwould support "Immediate UI" (uiMode: immediate). Here are some explainers:Proposal 1
Add a new option to
startAuthentication(for exampleuseImmediateUIMode) that configures the options passed tonavigator.credentials.getfor Immediate UI (like I did in #779). As there is still some movement about this API and only Chrome implements it yet, there might be breaking changes to this API in the future.Proposal 2
Add a new
getOptions: Partial<CredentialRequestOptions>option that is spread into the options passed tonavigator.credentials.getor maybe even better a callbackmodifyOptions: (options: CredentialRequestOptions) => CredentialRequestOptions(there is 100% a better name for both of these 😅). This way users are free to use options not supported bystartAuthenticationand are responsible for dealing with breaking changes.Once Immediate UI is more stable it can still be added as a supported option.