-
Notifications
You must be signed in to change notification settings - Fork 4
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
UX: change the behaviour of the filter dropdown #143
Comments
Hi @bunekcca, This is a reason and a consequence of my questions in point 1 at #91 (comment). With the current implementation, after selecting a format, only that format is present in the results and the Elasticsearch aggregations applied over the results don't see the other formats. This could be changed by using a
Now, my question is, where should we apply the text query and the date range? If we apply them in the Sorry for the long explanation, I hope it's clear enough to get your decision on how this should behave. If you decide to change the current behavior, it may take 6-8 hours to develop the changes. Best regards. |
Hi @jraddaoui Thanks for the explanations. I would follow your lead on that. |
When a user select a value in the dropdown and he wants to select one more value, he can't. He has to reset the filters to be able to select multiple values
Once a value is selected, the rest of the list should still appear to make multiselection available.
The text was updated successfully, but these errors were encountered: