Hi David, While I understand the ease of use that ListFilter bring in, my issues are
1. If there are multiple filters with multiple options, the user cannot at a glance see all the filters active / available without scrolling 2. when using multiple filters, the page is refreshed on each filter option Potential solution; To fix only 1 : When using the dropdown, the widget used is the same as *Charfield+options. *This is still a consistent design as ListFilters is built on a list of options*.* Moreover, since it is a standard form element, standard accessibility attributes can be used. Visually, the page can just show the filters available which is the immediate concern when looking at filters. To fix both, (which is out of scope unless someone is interested), we can treat list filters as a part of "Search Form" with an apply button. This will allow users to select multiple filters and apply the filters with a single request. Cordialement, Vasanth MOHAN On Fri, 4 Nov 2022 at 06:03, David Sanders <shang.xiao.sand...@gmail.com> wrote: > Hi Vasanth, > > What advantages does a dropdown have over simply placing the options there > though? Typically these sorts of things have horrendous accessibility and > make the code more complex. > > -- > David > > On Fri, 4 Nov 2022 at 02:17, Vasanth Mohan <vasanth93...@gmail.com> wrote: > >> Hello, >> >> When there are multiple filters on a model, the filter sidebar gets >> cluttered quite rapidly. Is there a specfic reason, we list the options >> over a dropdown? >> >> I'd like to see if there is support to change the default filter widget >> to dropdown? I'd like to reiterate, this merely replaces the list with a >> dropdown, this should not change anything at a functional level. Anything >> complex can continue to use third-party apps. >> >> Thanks >> Vasanth >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/a16ee31b-1f82-47c3-917c-56b8d3b7f892n%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/a16ee31b-1f82-47c3-917c-56b8d3b7f892n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/b_nzFu4gg7I/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CADyZw-7QTcHfsp0822DbvwpudGPxjY_ehKGvjxKifJ4_KdNUCg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CADyZw-7QTcHfsp0822DbvwpudGPxjY_ehKGvjxKifJ4_KdNUCg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAOAVv_P6FGYvKALtJ2FcobZ3seDmQ07Pi-Cz1fsnSYaEuV3ziA%40mail.gmail.com.
