Bug #2750
Browser back/forward buttons don't cause page to change
Start date:
05/20/2020
Due date:
% Done:
100%
Subtasks
History
#1
Updated by Luke Murphey over 4 years ago
Updated by - Status changed from New to In Progress
#2
Updated by Luke Murphey over 4 years ago
Qs:
- What is the best organization for this code?
- What are the things that main index is doing right now?
- Loading history
- Routing
- Route change handling
- ErrorBoundary
- Placing of main code in the HTML page
- Loading of main CSS
- How do I get the router to go off of the new history URL?
- Is there another Router I ought to be using?
- Am I using the history wrong?
- Should I use forceRefresh?
- Didn't work
- Should I use Redirect?
- How do I convert the URL from the update to something I can process?
- Am I using the correct history object?
- Switched to the one provided
- https://reacttraining.com/react-router/web/example/basic works without setting the history directly
- This works when changing pages, but not within a page
- [Partial Fix] Process the change event in componentDidUpdate()
- Set the state in history so that I can process this using History.replaceState() and process in componentDidUpdate()
- Wrap Approuter and have it re-render when route changes
- Render is called but read_work doesn't change
- Read work re-renders too but without a change
- Use Redirect
- https://stackoverflow.com/questions/41911309/how-to-listen-to-route-changes-in-react-router-v4
- https://stackoverflow.com/questions/39342195/intercept-handle-browsers-back-button-in-react-router
- https://stackoverflow.com/questions/59567624/react-how-to-use-componentdidupdate-for-updating-location-pathname
- https://developer.mozilla.org/en-US/docs/Web/API/History/pushState
- https://www.chenjianjx.com/in-react-router-dont-use-window-history-pushstate-but-history-push/: already doing this
- https://medium.com/@ivantsov/using-react-router-and-history-38c021270829
#3
Updated by Luke Murphey over 4 years ago
- Subject changed from Back/forward buttons don't cause page to change to Browser back/forward buttons don't cause page to change
#4
Updated by Luke Murphey over 4 years ago
- Status changed from In Progress to Closed