-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Next 13 with App Router and Streaming Enabled causes issues with Browser Navigation & RefinementList Widget #5987
Comments
Hey @Haroenv - I also noticed that when we click any widget action (like refinement or pagination etc), it triggers a repeated call to the same route via Here's the short video: So Next said that using useRouter.push(url) will call that route dynamically but I believe to make our widgets interactive we donot need to use this and instead we can use native JS: |
Hi @syed-yawar, thanks a lot for the reproduction and videos ! I'll add this to our backlog. About the use of There might be valid reason to use Thanks again ! |
Hi @syed-yawar I've had a look into it and it's because when pressing the back button, the loader from This seems more like an issue on Next's side (or the canary version of React they use) as it seems to have been fixed as of Can you please try and let me know if it works ? |
Hello @aymeric-giraudet , I've conducted tests on the latest version of Next, which is |
🐛 Current behavior
When streaming is enabled, routing does not work as expected and it also throws an error related to refinement.
🔍 Steps to reproduce
Please watch this recording for better understanding
https://www.loom.com/share/5a2b54810cbe415586ba6e66db6e530a?sid=170f8918-dc0e-4865-b69b-71ebe11669c8
Live reproduction
https://codesandbox.io/p/sandbox/dazzling-cdn-c2flwn
💭 Expected behavior
Ensure Browser Navigation Functions Accurately with Streaming Enabled on Next 13/14 and App Router and render the correct data
Package version
react-instantsearch-nextjs 0.1.7
Operating system
all
Browser
all
Code of Conduct
The text was updated successfully, but these errors were encountered: