aws-amplify / aws-amplify/amplify-studio
Input caret skips to end of text box in Authentication > MFA > SMS Message
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
N/A
### Region
N/A
### Environment name
N/A
### Figma File Version (if applicable)
_No response_
### Amplify CLI Version
_No response_
### If applicable, what version of Node.js are you using?
_No response_
### What operating system are you using?
Windows 11
### Browser type?
Google Chrome 116.0.5845.188 (Official Build) (64-bit) (cohort: Stable)
### Describe the bug
When attempting to edit the MFA SMS message, the caret skips to the end of the input field after every key press.
### Expected behavior
The input caret should remain in the correct place
### Reproduction steps
1. In Setup > Authentication, select Optional or Enforced MFA
2. Attempt to edit the SMS message by placing the caret in the middle of the message
3. Note that the caret jumps to the end of the input after every key press

### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start by reproducing the issue in Setup > Authentication with Optional or Enforced MFA, then edit the SMS message with the caret placed in the middle. Trace the Authentication > MFA > SMS Message input entry point and verify that the caret remains at the intended position after each key press.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100