Fix/Autocomplete issue has been fixed #442
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blazedglimmer
changed the title
shubhamsyal007
approved these changes
Apr 2, 2024
matthewmedia
approved these changes
Jun 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It resolves the issue with OTP autocompletion.
Any background context you want to provide?
Imagine a scenario where we've integrated this library into mobile devices. When a user receives an OTP on their device, the code appears on the keyboard for autocompletion instead of manual typing. However, clicking on the OTP previously only completed one digit. With this PR, I've updated the autoComplete field value from 'off' to 'one-time-code'. Now, users have the option to autofill the entire OTP once it's received.