Component: p-dropdown emits changes when selected option did not change #14788
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Milestone
Describe the bug
We recently updated from PrimeNG 15 to 17.
There seems to be a change in the behavior of the p-dropdown component:
Back in v15, when selecting the already selected option in a p-dropdown again, no change would be emitted. Now in v17 it does seem to do so.
The issue can be cruedly reproduced using the official component docs:
V15:
![15_4 behavior](https://private-user-images.githubusercontent.com/20710097/304012440-cf315d5b-3497-4e75-82f3-4674b625ea22.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMTYxNzAsIm5iZiI6MTczOTMxNTg3MCwicGF0aCI6Ii8yMDcxMDA5Ny8zMDQwMTI0NDAtY2YzMTVkNWItMzQ5Ny00ZTc1LTgyZjMtNDY3NGI2MjVlYTIyLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDIzMTc1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJlZTJiMzJjMDRjODEyNDBlYTg2MTQwYTgyMTY1Zjg4ZmZlMDFkZWZiMDFhODliZTE2YzdiZDliMmIwY2E2MTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.PUs3QWw64yemmPZGwzpiAImsbKFXKCXu2zoEqNFSS8c)
V17
![17_6 behavior](https://private-user-images.githubusercontent.com/20710097/304012466-73c791f7-5e81-41c9-a138-50d65d027e51.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMTYxNzAsIm5iZiI6MTczOTMxNTg3MCwicGF0aCI6Ii8yMDcxMDA5Ny8zMDQwMTI0NjYtNzNjNzkxZjctNWU4MS00MWM5LWExMzgtNTBkNjVkMDI3ZTUxLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDIzMTc1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJjMjM5ODFlNGMyZGQxZjQ1OTI1OGFmZTdjMTk5MTcxYWEzMGY2OGFkNzk1ZmQ0YTE3NzBjMDg5ZTQ5ZTljYTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.PItife45y_O2scfC8F5noj1ZxhUPSkxJuL3Tk0VCzIY)
The question is: Is this new desired behavior or a regression?
Environment
primeng: 17.6
angular: 17.1
Reproducer
No response
Angular version
17.1.0
PrimeNG version
17.6.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.16.0
Browser(s)
Chrome 120
Steps to reproduce the behavior
Open the docs on v15 and v17 as described above:
v15: https://www.primefaces.org/primeng-v15-lts/table#filter-row
v17: https://primeng.org/table#filter-row
Expected behavior
We would expect no emission of a change by p-dropdown when the already selected option is clicked again in the p-dropdown.
The text was updated successfully, but these errors were encountered: