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

[Bug] Dropdown position not always correctly updated with virtual scrolling #1023

Closed
wants to merge 1 commit into from

Conversation

HDinger
Copy link

@HDinger HDinger commented Jan 16, 2019

Description

The dropdown of the multi-select is not always correctly positioned when the virtual scrolling is enabled. This happens because there is a case in which the promise after updating the list items is not resolved. Thus the list position is not updated.

ng-select-dropdown-position

https://stackblitz.com/edit/angular-hxjvkx

@coveralls
Copy link

Coverage Status

Coverage increased (+0.003%) to 94.776% when pulling 779c6ac on HDinger:master into c7dd2ac on ng-select:master.

@HDinger
Copy link
Author

HDinger commented Apr 15, 2019

@varnastadeus Could I please get a comment on this? :)

@EricsG95
Copy link

Yes this PR is very critical, as I am using too and it is very common to have greater amount of entries and virtual scrolling is required. One of a common practiced in the usage of select is to keep the list between 3 - 12. Hence a virtual scroll and a search box will come in handy. Hence there is a need to have the virtual scrolling to works correctly.

@oliverguenther
Copy link
Contributor

Can we do anything to move this forward? We're still running on a fork due to this issue :-/

@varnastadeus
Copy link
Member

closing in favor #1188

varnastadeus added a commit that referenced this pull request Jun 25, 2019
* fix: don't fire scroll to end when scrollTop = 0
fixes #1018

* feat: adjust dropdown position on selection when multiple and appendTo
closes #984

closes #899

closes #890

closes #1018

closes #1023

closes #1144

closes #1095

closes #1122

closes #1163

closes #955
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants