Currently when you set a new min or max range the page is reloaded and the slider scale is recalculated: outer left is the new minumum and outer right the new maximum.

Depending on your range this can be an undesired result because a user can't slide back left (or right for max) to a wider range. In my usecase I only have an integer range from 1-18 and would like to keep the scale static so users can for example pick a range from 4-10 and then slide back to 2-15.

I think this would be a pretty useful feature. What do you guys think?

Comments

davidseth’s picture

davidseth commented

+1

Anonymous’s picture

Anonymous (not verified) commented

The solution requires to query the actual min/max values for the given activeFilters, but excluding itself. I have this implemented in the Search API ranges module (also a slider module, but for Search API). Keep in mind it's a costly feature, because it requires 2 extra search queries per slider, per page-view. Namely to find the 'min' and 'max' values.

Now I'm trying to make my module work with Facet API, or at least to work with the Facet API Current Search block.

nick_vh’s picture

nick_vh
he/him
Location Ghent
commented
Status: Active » Closed (won't fix)

I tried fixing this in the latest version of the apachesolr patch. This is actually a task of the queryType. So I'm closing this issue.
We do need caching of these stat fields but that is up to the queryType (in our case numeric_range)

If the last patch from facetapi will be applied this widget will not appear if numeric type is not present as queryType plugin