You can and should not disable the browser back button or history. That’s bad for user experience. There are JavaScript hacks, but they are not reliable and will also not work when the client has JS disabled. Your concrete problem is that the requested page is been loaded from the browser cache instead of straight … Read more
tl;dr your best bet is to use a store like redux or mobx when managing state that needs to be accessible throughout your application. Those libraries allow your components to connect to/observe the state and be kept up to date of any state changes. What is a <Route>? The reason that you cannot pass props … Read more
location.replace(“#hash_value_here”); worked fine for me until I found that it doesn’t work on IOS Chrome. In which case, use: history.replaceState(undefined, undefined, “#hash_value”) history.replaceState() operates exactly like history.pushState() except that replaceState() modifies the current history entry instead of creating a new one. Remember to keep the # or the last part of the url will be … Read more
5.5.9.1 Event definitions The popstate event is fired in certain cases when navigating to a session history entry. According to this, there is no reason for popstate to be fired when you use pushState. But an event such as pushstate would come in handy. Because history is a host object, you should be careful with … Read more