Great module, but the user interface is a little confusing. As a user clicking on a search icon, I would expect that my results would be filtered by that icon, not my list of choices. So I might think that I am trying to find all entries (nodes, terms, etc) with those letters, rather than the true effect that I am just filtering my list options and that I must still select an actual item from my dropdown.
This is particularly confusing since the search criteria that I type actually seems to appear as one of the filter choices (ie if I am searching for "bre," --bre-- appears as a select choice. If a user then clicks on "apply" to filter results for that choice they naturally get an error.
My dropdowns have a hierarchy which is already using the "--" prefix for terms so it looks extremely similar.
If the search letters could be removed from the select list that would be better.

It would be great if the user could see the result list changed as they type letters (like with autocomplete) instead of having to click the search icon again. In my mind I don't think of having to click the same button to do 2 different things (get to the search box, and then later limit my list).
Is it possible any time soon that the dropdown can be filtered "on-the-fly"?

Comments

shark’s picture

shark commented

That'd be an awesome feature to have.

I wonder if it would be hard to have a configuration option which would turn the select dropdown into a text field (either as soon as the form loads or only after the search icon is clicked), and the textfield would act like the Google AJAX search box.

So the user would see this:

Select: [              ]

then the user types in 'Foo' in the textfield, and the dropdown displays the options Foo Bar and Foo Baz:

Select: [Foo           ]
        [Foo Bar       ]
        [Foo Baz       ]