Quasar: [Request] DataTable Filter Column Headers
This is similar to SharePoint functionality for data tables, basically for each column header (if filterable), you'd get a pretty select dropdown to choose, integrated into the data table. My demo here doesn't support multi-select, but an option to single or multi-select filters would make this perfect.
Async0x42
All 5 comments
Nice idea. Will see about it.
rstoenescu
on 30 Jan 2017
I would like to add that it would be great if the column headers and filters could be designed so that they are also reachable via keyboard/tab browsing.
kdmon
on 19 Mar 2018
I find that in many cases using column headers is too limiting and you want to filter by something that isn't visible. Also this ties the filtering to the presentation and you run into issues where the filter needs more width than the column and so you are wasting table width for wide filters. A huge improvement IMO is using chips and a list of filter options. An excellent example is seen on Intercom.com's user list:
Note, a component implemented in this way would be useful for more than just tables, it could be used for filtering lists, points on a map, a grid full of tiles, etc. So I think not only is it more powerful and user-friendly, it is also more re-usable.
colinmollenhour
on 13 Jul 2018
Hi,
The new QTable (introduced in v0.14 if I'm not mistaken) allows for total customization, so this can be done in app-space now.
rstoenescu
on 19 Aug 2018
@rstoenescu Can you elaborate on this? I need to create column filters that will work with the search filter as well.
kevrousso
on 9 Mar 2020
Related issues
mesqueeb
路
3Comments
victorborgaco
路
3Comments
tombarfoot
路
3Comments
sskwrl
路
3Comments
fnicollier
路
3Comments
Most helpful comment
I find that in many cases using column headers is too limiting and you want to filter by something that isn't visible. Also this ties the filtering to the presentation and you run into issues where the filter needs more width than the column and so you are wasting table width for wide filters. A huge improvement IMO is using chips and a list of filter options. An excellent example is seen on Intercom.com's user list:
Note, a component implemented in this way would be useful for more than just tables, it could be used for filtering lists, points on a map, a grid full of tiles, etc. So I think not only is it more powerful and user-friendly, it is also more re-usable.