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

Automplete: autoHighlight=true option no longer works in latest primeng version #15663

Closed
nevius opened this issue May 23, 2024 · 3 comments
Closed
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@nevius
Copy link

nevius commented May 23, 2024

Describe the bug

I recently upgraded from primeng 16.1.0 to 17.17.0
Now, in the autocomplete component, autoHighlight=true no longer automatically selects the first element in the list of suggestions.

Environment

Angular app using primeng.

Reproducer

https://stackblitz.com/edit/4shexj?file=src%2Fapp%2Fautocomplete-objects-demo.html

Angular version

17.3.9

PrimeNG version

17.17.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.10.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Open StackBlitz example
  2. Type "United" into the text input

Expected behavior

Expected: "United Arab Emirates" suggestion is highlighted and can be selected by hitting Enter key.
Actual: No suggestion is highlighted.

@nevius nevius added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 23, 2024
@nevius
Copy link
Author

nevius commented May 23, 2024

I just checked the code and it seems that this behavior is now controlled by the autoOptionFocus option. Maybe the documentation should be updated.

@Petar-CV
Copy link

Hm, we're having the same issue in one of our projects running PrimeNG 17.18.2
Did you manage to bypass it using autoOptionFocus? @nevius

@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

3 participants