Add setTimeout back to unstable_usePrompt #10718
Merged
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.
Add back in the
setTimeout
that was removed in #10687 since it causes issues withnavigate(-1)
. This wasn't specifically removed to fix anything in the original bug.I wasn't able to get a unit test exposing this though because it seems to be some sort of race between
window.history
andwindow.confirm
where thewindow.history
revert operation doesn't land until after thewindow.confirm
. This doesn't happen in a unit test with a mockedwindow.confirm
.Closes #10714