I’m encountering an issue with the filtering system.
When I apply a filter (e.g. selecting an attribute), the page reloads and the filtering works correctly the first time.
However, the problem occurs when I try to apply a second filter or modify the initial selection. At that point, range-type filters (such as size sliders) get applied automatically — even though the user has not interacted with them.
This behavior causes unexpected filtering and incorrect results for the user.
Steps to Reproduce:
Load the archive page with filters.
Apply a filter (e.g. select a color or category).
Page reloads and the result is filtered correctly.
Now modify the filter:
Either remove the first selection and add another,
Or keep the first and add a second selection.
Without touching the range filters, they automatically apply and start filtering the results.
Expected Behavior:
Range filters should not be applied unless the user explicitly selects or interacts with them.
if you look carefully, the range filters actually change - it auto-recalculates after successful filtering. So when you filter the second time, it will also consider those new auto-recalculated values.
But, starting from 2.0-alpha, you will have the option below, that you will be able to toggle, that will prevent this recalculation, and then it should work like you intended.
Thank you for your detailed response. I read it carefully, but I must respectfully disagree — I believe this is a bug, and I’d like to explain why.
I completely agree that range filters should auto-adjust based on the query results — this is both expected and useful behavior. However, the problem arises when the filter logic doesn’t reset correctly between queries.
Here’s what I mean:
Let’s say I apply a checkbox filter (e.g., filter A). The filtering works fine, and the range filters are correctly recalculated to reflect the new dataset.
But if I then remove filter A and reapply filtering, the range filters stay applied with the previous auto-adjusted values — even though the user never interacted with them. This silently reduces the number of visible results, which is confusing and incorrect from a UX standpoint.
As for the upcoming option you mentioned in 2.0-alpha: while I appreciate that, disabling the recalculation altogether would also remove the dynamic adjustment of min/max values, which is a feature I find very helpful and would prefer to keep.
To summarize:
Range filters should dynamically adapt, but only to the current query, they should not persist values derived from a previous filter state if the user never interacted with them directly.
Thank you for your detailed answer. I sincerely appreciate it. I retested this again, and I agree with you. Especially as you mentioned that you would like to keep dynamic adjustments of range filters, which would not happen if you toggle that option on.
I retested, recorded a video and created an internal task for this. Once it’s improved, or we have news on this, we will update this topic.
