Set and increase the choice.js option searchResultLimit

[low-res]

Not a real bug, but still quite annoying: If you have to choose from a large number of user groups for the recipients, you have the problem that only four results are always given for selection when using the search. Even if many more options would actually match the search term.

This is because Choice.js only displays 4 options as search results by default. You could increase this value with the searchResultLimit option (https://github.com/Choices-js/Choices?tab=readme-ov-file#searchresultlimit-4).

It would be nice if this value was set and contained a sensible value like 10 or more?!

The change would be very simple. In luxletter/Resources/Public/JavaScript/Luxletter/Choices.min.js the optin just need to be set:

window.luxLetterReceiverChoice = new Choices(e, {allowHTML: !0, searchResultLimit:25})

[einpraegsam]

Thanks for your ticket. I just tested it again. I see 7 results. As far as I remember, we deliberately didn't want to display too many entries so that the options could still be seen on small screens.

Or do I understand your request wrong?

[low-res]

Hi @einpraegsam . Yeah as long as you do not search for something the list is complete and shows all options (and the list is scrollable!)

But as soon as I start typing, the list always only shows 4 options (even if there are more options that need to be shown) and the list is not scrollable.

[einpraegsam]

Ok, that seems to be correct. We could increase the size also to 7 if this would help you?
BTW: Your LUXletter version seems to be older and you would have to update to the latest version of course

[low-res]

To prevent problems like that, I think you should set the value pretty high. e.g. 100.

I just tried it out. The height of the visible optionslist is always 7 items. If the searchresults are more, the list gets scrollable.
So, the option searchResultLimit really means the max number of possible options and not the visible height of the optionslist. So a high value for searchResultLimit should always be fine-

I also found this issue Choices-js/Choices#1118 with a similr problem. But a value of -1 did not work in my tests.