Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InputOtp: Android Phones - MoveToNext is not called after input #15846

Closed
televicDev opened this issue Jun 14, 2024 · 1 comment
Closed

InputOtp: Android Phones - MoveToNext is not called after input #15846

televicDev opened this issue Jun 14, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@televicDev
Copy link

Describe the bug

If you use an Android Phone to input characters in the InputOtp component, multiple characters are inserted in the same input element.

Environment

Android Phone - Samsung A54 & A55
Reproduceable on the PrimeNG demo

Reproducer

No response

Angular version

17.3.5

PrimeNG version

17.18.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.20.2

Browser(s)

Chrome on Samsung phone

Steps to reproduce the behavior

Type into the input field on a real device.
All of the characters are added to the first input.

The behavior is OK on emulators and can only (for us atleast) be reproduced on real devices

Expected behavior

I expect that after inputting a character the focus is moved to the next input but instead all of the characters I am inputting are added to the same input.

Screen_Recording_20240614_153855_Chrome.mp4
@televicDev televicDev added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jun 14, 2024
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants