Workaround broken back/forward #245
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erikras
added a commit
that referenced
this pull request
Sep 27, 2015
Workaround broken back/forward. Fixes #240
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#240
This snuck in when I changed
history.listentohistory.registerTransitionHook.So we're back to the URL updating synchronously before the transition. I'm unsure why the
listenBeforeisn't fired by browser history. Is it a bug or should it behave this way?A more robust solution is required. I feel like it should be found in react-router's
useRoutesbut it will have to wait for a day or 2.Apologies!