[59732] List is scrollable even if there is only 1 item#22814
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
HDinger
force-pushed
the
bug/59732-list-is-scrollable-even-if-there-is-only-1-item
branch
from
77e806d to
117a403
Compare
oliverguenther
approved these changes
Apr 20, 2026
…the additional create option is displayed
HDinger
force-pushed
the
bug/59732-list-is-scrollable-even-if-there-is-only-1-item
branch
4 times, most recently
from
48371e8 to
5fb468a
Compare
HDinger
force-pushed
the
bug/59732-list-is-scrollable-even-if-there-is-only-1-item
branch
from
5fb468a to
3dd3d91
Compare
oliverguenther
approved these changes
Apr 22, 2026
HDinger
deleted the
bug/59732-list-is-scrollable-even-if-there-is-only-1-item
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
https://community.openproject.org/wp/59732
What are you trying to accomplish?
What approach did you choose and why?
ngSelect had quite same changes in the meantime. The biggest change was making
searchTermprivate. Thus we were forced to use thefiltermethod which directly opens the autocompleter. On the global search, that caused some issues as it initally opened the search on page load. That is why I did an ugly workaround and used the privatesearchTermthere.