feat(input-otp): add new input-otp component#30386
Merged
brandyscarney merged 83 commits intofeature-8.6from May 29, 2025
Merged
feat(input-otp): add new input-otp component#30386brandyscarney merged 83 commits intofeature-8.6from
brandyscarney merged 83 commits intofeature-8.6from
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
package: core
|
Thank you, @brandyscarney, for your work on this component. One feature suggestion: pressing CTRL+A (or CMD+A on macOS) inside the component could select and clear all input fields at once. This would align with common input behavior and improve UX for users needing to re-enter their code quickly. Example: https://input-otp.rodz.dev/ |
thetaPC
reviewed
May 27, 2025
Contributor
thetaPC
left a comment
thetaPC
left a comment
There was a problem hiding this comment.
No issues found with core and Angular. I'm waiting on React and Vue to be ready for review.
thetaPC
reviewed
May 28, 2025
…the value changes
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Issue number: internal
What is the current behavior?
In order to re-create an OTP Input component users have to custom style an
<ion-input>, possibly multiple, to get the design and functionality they want.What is the new behavior?
ion-input-otpwhich provides the OTP input functionalitytypewhich determines whether the boxes accept numbers or text/numbers and determines the keyboard to displayinputmodepropertylengthproperty to control the number of input boxesfill,shape,size,colorseparatorsproperty to show a separator between 1 or more input boxesdisabled,readonlyand invalid statespatternpropertyionInput,ionChange,ionComplete,ionBlur,ionFocussetFocusDoes this introduce a breaking change?
Other information
Previews
Documentation