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
In order to provide a reliable canGo(n) implementation in browsers, we need to know the length of the current session history. This would also allow us to return a boolean value from go(n) so callers could know if the navigation actually succeeded or not.
The way to do this would be to keep a current value in session state. I think we could reliably do this if we refactored BrowserHistory to use sessionStorage the same way that HashHistory does.
The text was updated successfully, but these errors were encountered:
@taurose Yes, exactly. Sorry, when you submitted #843 I wasn't yet capable of understanding everything that was going on there. I needed a little time to think over the problem myself so I could get it.
If you're up for it, I'd definitely welcome that functionality now. Maybe we could roll it into #1376?
In order to provide a reliable
canGo(n)
implementation in browsers, we need to know the length of the current session history. This would also allow us to return a boolean value fromgo(n)
so callers could know if the navigation actually succeeded or not.The way to do this would be to keep a
current
value in session state. I think we could reliably do this if we refactoredBrowserHistory
to usesessionStorage
the same way thatHashHistory
does.The text was updated successfully, but these errors were encountered: