-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Dropdown filtering issues with array of strings #14011
Comments
Also found it |
Yeah , the same issue here! |
Same issue after last update. |
Hi, Thanks a lot for reporting the issue, could you please also share a stackblitz example so we can identify the root cause clearly? |
Hi everyone, With version 16.7.0, we have released the first part of the accessibility implementation for inputs that we have been working on for a long time. Based on the research we conducted during the implementation, we decided that many components needed changes in their structure and simplification, and these components were rewritten. Unfortunately, after extensive testing, there may be unexpected and unforeseen bugs that have emerged. We are grateful for your reports, and we are working to address them in the upcoming release! |
Hi. I'm still having problems with the dropdown filter in versions bigger than 16.6.0. I get the error 'TypeError: option.indexOf is not a function' in file 'node_modules/primeng/fesm2022/primeng-dropdown.mjs' every time i filter. This is happening with at least versions 16.9.1 and 17. I had to downgrade to 16.6.0 even though i'm using angular 17. The Multiselect filter is also not working properly. |
Describe the bug
The dropdown filtering with array of strings works incorrectly. I have the dropdown like this.
Bug 1: The empty text doesn't show when no data is found.
Bug 2:The filtering totally doesn't work with string array
Bug 3: After clear get "[object PointerEvent]" as value
Environment
Angular: 16.2.7
PrimeNG: 16.7.0
Browser: Chrome (Latest)
Reproducer
No response
Angular version
16.2.7
PrimeNG version
16.7.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.16.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: