feat(input-otp): convert to a form associated shadow component #30785#30884
Merged
brandyscarney merged 56 commits intonextfrom Feb 5, 2026
Merged
feat(input-otp): convert to a form associated shadow component #30785#30884brandyscarney merged 56 commits intonextfrom
brandyscarney merged 56 commits intonextfrom
Conversation
…ed and required change
thetaPC
approved these changes
Jan 16, 2026
Contributor
thetaPC
left a comment
There was a problem hiding this comment.
LGTM, one comment but not a blocker
ShaneK
approved these changes
Jan 28, 2026
Member
ShaneK
left a comment
There was a problem hiding this comment.
Looking good! I left a couple of comments, but I consider them non-blockers. Well done!
ShaneK
approved these changes
Feb 5, 2026
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
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?
Input Otp uses
scopedencapsulation. This causes issues with CSP compatibility and is inconsistent with our goal of having all components use Shadow DOM.What is the new behavior?
ion-input-otptoshadowwithformAssociated: trueDoes this introduce a breaking change?
Other information