You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to implement this for ajax-chosen on iceslice.
When you click on the chosen widget initially, if it contains no values you can type in a search string which it uses. However, it should also be capable of doing an iniitial query, such as to request the first 10 or 50 entries from the system. If you could continue in this manner to scroll too, that would be good, but not necessarily critical.
Perhaps an initial query might not even be necessary. Perhaps you can support merging both queried results AND initial results (when the page loads).
The text was updated successfully, but these errors were encountered:
i think we are talking about the same thing. this is, for example, how Select2 shows all the select choices when it is first opened - the query function matches all options when search is empty.
so, if you do not set the minimumInputLength parameter, or set it to zero, query() is called when the select2 is opened and returned choices will be displayed right away.
I had to implement this for ajax-chosen on iceslice.
When you click on the chosen widget initially, if it contains no values you can type in a search string which it uses. However, it should also be capable of doing an iniitial query, such as to request the first 10 or 50 entries from the system. If you could continue in this manner to scroll too, that would be good, but not necessarily critical.
Perhaps an initial query might not even be necessary. Perhaps you can support merging both queried results AND initial results (when the page loads).
The text was updated successfully, but these errors were encountered: