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
It looks like the package is using history.pushState instead of history.replaceState.
It would be nice if I could scroll around with hash spy enabled and not have it impact how many times I have to hit the browser back button to navigate to the previous page.
I have a use case for this as well, however I'm not sure that replacing pushState with replaceState is the best solution... maybe making push vs replace an additional prop you can pass? Or making the hashSpy prop a configuration object instead of just a boolean?
It would be nice to have the option to configure this behavior.
Uh oh!
There was an error while loading. Please reload this page.
It looks like the package is using
history.pushState
instead ofhistory.replaceState
.It would be nice if I could scroll around with hash spy enabled and not have it impact how many times I have to hit the browser back button to navigate to the previous page.
Reference: https://stackoverflow.com/questions/2305069/can-you-use-hash-navigation-without-affecting-history
The text was updated successfully, but these errors were encountered: