[2.x] Fix issue where initial page data is coming from history state #2023
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.
When we initially decrypt the history state so that the router can
restore
any remembered data, we were setting it as thecurrent
history in theHistory
class, causing the page to be loaded from that state rather than the initial page props on the page.The page would then load the initial page props, but you'd get a flash of stale data.
This fixes that issue by storing the
restore
data as a separate one-time-use property.