You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
As mentioned in the Next.js documentation, we can also modify the history stack using window.history.pushState or replaceState.
Imagine there is a gallery, and you want to change the page URL when the user swipes to the next artwork. This way, if they refresh the page, they will see that particular artwork again. Additionally, using searchParams is not an option for us in this scenario.
So, what if we could set a ref or state right before programmatically manipulating the history stack, and this prevents the loader from showing up at the top of the page?
Reproduction steps
.
Screenshots
![DESCRIPTION](LINK.png)
Logs
No response
Browsers
Chrome
OS
Mac
The text was updated successfully, but these errors were encountered:
Description
Hi,
As mentioned in the Next.js documentation, we can also modify the history stack using
window.history.pushState
orreplaceState
.Imagine there is a gallery, and you want to change the page URL when the user swipes to the next artwork. This way, if they refresh the page, they will see that particular artwork again. Additionally, using searchParams is not an option for us in this scenario.
So, what if we could set a ref or state right before programmatically manipulating the history stack, and this prevents the loader from showing up at the top of the page?
Reproduction steps
.
Screenshots
![DESCRIPTION](LINK.png)
Logs
No response
Browsers
Chrome
OS
Mac
The text was updated successfully, but these errors were encountered: