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
Platform and Target: [e.g. iOS 11 Cordova app, or Android 8 Chrome browser]
Live Link or CodeSandbox: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP). You can start from forking the following CodeSandbox template: CodeSandbox
Describe the bug
Navigating back to current URL a second time with an async route leaves allowPageChange incorrectly set to false after routing has completed.
Related to #2200. The fix for #2200 in 83abadd only addresses navigate, and missed applying the same fix on back
Describe the bug
Navigating back to current URL a second time with an async route leaves
allowPageChange
incorrectly set to false after routing has completed.Related to #2200. The fix for #2200 in 83abadd only addresses
navigate
, and missed applying the same fix onback
To Reproduce
Reproduction app at https://codesandbox.io/p/sandbox/eager-kepler-ozg9yr
Steps to reproduce the behavior:
allowPageChange
remains falseExpected behavior
At step 5,
allowPageChange
should return totrue
once the back command completes without updating the page.Actual Behavior
At step 5,
allowPageChange
incorrectly remainsfalse
once the back command completes without updating the page.The text was updated successfully, but these errors were encountered: