Skip to content

Conversation

@Haroenv
Copy link
Contributor

@Haroenv Haroenv commented Jan 30, 2026

Summary

URL parameters should be clamped to either the min/max range, or otherwise the min/max of the range from the search responses. This clamping should only be visible, the actual parameter should still be applied

Result

fixes #6881

URL parameters should be clamped to either the min/max range, or otherwise the min/max of the range from the search responses. This clamping should only be visible, the actual parameter should still be applied

fixes #6881
@codesandbox-ci
Copy link

codesandbox-ci bot commented Jan 30, 2026

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 6af9b89:

Sandbox Source
example-instantsearch-getting-started Configuration
example-react-instantsearch-getting-started Configuration
example-react-instantsearch-next-app-dir-example Configuration
example-react-instantsearch-next-routing-example Configuration
example-vue-instantsearch-getting-started Configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RangeSlider widget overflows its bounds when you set a max value in the URL higher than the data in the index

1 participant