-
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
Component: P-dropdown has issue while removing items.Scroll is not happening Properly #17130
Comments
I tried implementing logic like this which is working but when i have appendTo Body. it doesn't work This needs to be fixed |
Due to PrimeNG team's busy roadmap, this issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨ |
@acharugulla Screen.Recording.2024-12-20.at.14.43.28.mov |
Hi @qwadrox I am calling scroll function each time , based on some conditions. It should work automatically. There are 100's of p-dropdown You this issue needs to be fixed |
I have provided you a solution |
Describe the bug
Primeng dropdown scroll is buggy, when user removes value in editable dropdown. It doesn't scroll to correct value
Environment
Angular
Reproducer
No response
Angular version
17
PrimeNG version
17
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20
Browser(s)
Chrome,Safari , Edge
Steps to reproduce the behavior
Assume you have editable prime ng drop down which has values from 1 to 500. User enters a value in editable dropdown as 300. The dropdown opens and scrolls to 300. But when user erases value (assume 0), then value will be 30, dropdown should scroll to 30
and its not happening
I tried implementing logic like this which is working
https://stackblitz.com/edit/ejxbx3fy?file=src%2Fapp%2Fdropdown-editable-demo.ts,src%2Fapp%2Fdropdown-editable-demo.html
but when i have appendTo Body. it doesn't work
This needs to be fixed
Expected behavior
It should scroll to 30 when user removes 0 in that
The text was updated successfully, but these errors were encountered: