-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 not selected After upgrade Primeng 16 #14094
Comments
Hi, 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 releases! |
@cetincakiroglu Thanks for update, hope it will solved soon. |
This also happens when using pTemplate So this does not work, because the <ng-template let-item pTemplate="selectedItem">
{{ item.label }}
</ng-template> So if we have an item like this
The <ng-template let-item pTemplate="selectedItem">
{{ item}}
</ng-template> This doesn't throw an error, but it also not the desired behavior. |
Behavior is the same as before the accessibility for the templating, please do not provide optionValue if you're provided optionLabel with templating. So in this case, please use it by considering our templating demos. Also, we're currently fixing dropdown bugs, please share a stackblitz reproducer of your issue too so we can check if we covered as many issues as we can. |
Hi @ashikjs, I've just pushed a commit to fix the issues you mentioned, the issue was caused by misinformation in the documentation as well and we found that label and model update logic is malfunctioning. When using For example:
As in the example, the option value will be Thanks for reporting the issue! |
Not working after PrimeNG 16.8.0 update.
=> These behaviors work in PrimeNG 16.6.0 and before |
Not working on the dropdown with filter. When I select an option the dropdown turns blank. If I remove optionValue it works normal, but I need the value to save to database.
|
Hi
|
I also faced same issue @rbarbeito , did you find any other solution apart from editable which would work as expected. |
I had the same issue, and the bug appears when I initialize my options at the declaration.
make the bug append
And the selected item is displayed. |
@guedru I have reviewed my code after your suggestion and it works correctly, thanks for the contribution. |
@guedru also worked for me, thanks you suggestion. |
Describe the bug
Dorpdown component value or name if we change then it's not working properly. I's not working reactive form and ngModel both.
Just add those to your drop-down option component :
Example: 1. https://stackblitz.com/edit/qxhoel?file=src%2Fapp%2Fdemo%2Fdropdown-reactive-forms-demo.html,src%2Fapp%2Fdemo%2Fdropdown-reactive-forms-demo.ts
Reproducer
https://stackblitz.com/edit/qxhoel?file=src%2Fapp%2Fdemo%2Fdropdown-reactive-forms-demo.html,src%2Fapp%2Fdemo%2Fdropdown-reactive-forms-demo.ts
Angular version
16
PrimeNG version
16.7.2
Expected behavior
it should show selected options as it is.
The text was updated successfully, but these errors were encountered: