Modify ↓
Opened 3 months ago
Last modified 3 months ago
#24465 new defect
Setting blank filter in search panel shouldn't select everything
| Reported by: | francois.lacombe | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | search, filter, select all | Cc: |
Description
Dear maintainers,
I came across a particular UX experience recently regarding the search panel.
Setting no (or blank) filter in this panel selects everything that exist in the active data layer.
Shouldn't it select nothing instead?
I didn't find this question already answered in existing tickets
Attachments (0)
Change History (2)
comment:1 by , 3 months ago
comment:2 by , 3 months ago
Why not, it's fine for me to disable the search button until the filter is set :)
Note:
See TracTickets
for help on using tickets.



I think it worked like that for a long time. I think the result is undefined, so maybe the "Start search" button should be disabled?