You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This solution also allows the TAB-key to navigate between the multiple-input-fields. If you don't want that, you would have to pass the index as well and do that on the last field only.
Environment
Windows 10
Angular 18.2.0
MS Edge 128.0.2739.63
Firefox 128.2.0esr
Reproducer
No response
Angular version
Angular 18.2.0
PrimeNG version
17.18.10
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.18.0
Browser(s)
MS Edge 128.0.2739.63
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered:
rehdie
changed the title
Component: Otp Input Component
Component: Otp Input Component does not focus next element when TAB is pressed in last input
Oct 28, 2024
mertsincan
added
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
and removed
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Nov 18, 2024
Describe the bug
When all input fields are filled and you want to move to the next form-element via TAB-key, nothing happens.
The reason is, that the method onKeyDown calls preventDefault in this case,
As a workaround I've done the following:
And in the component class:
This solution also allows the TAB-key to navigate between the multiple-input-fields. If you don't want that, you would have to pass the index as well and do that on the last field only.
Environment
Windows 10
Angular 18.2.0
MS Edge 128.0.2739.63
Firefox 128.2.0esr
Reproducer
No response
Angular version
Angular 18.2.0
PrimeNG version
17.18.10
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.18.0
Browser(s)
MS Edge 128.0.2739.63
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: