ref(browser): Update supportsHistory check & history usage#14696
Merged
ref(browser): Update supportsHistory check & history usage#14696
supportsHistory check & history usage#14696Conversation
Contributor
size-limit report 📦
|
fe76964 to
cc7dc32
Compare
cc7dc32 to
b034c35
Compare
❌ 3 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
AbhiPrasad
reviewed
Dec 13, 2024
Contributor
AbhiPrasad
left a comment
There was a problem hiding this comment.
Change LGTM! But I think the diff got messed up during the rebase.
b034c35 to
bbefd73
Compare
This file contains hidden or 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
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.
We had some elaborate check in there for
window.historywhich is based on very old (~2016) issues, which should not be an issue anymore in versions we support today. So we can streamline this quite a bit!Additionally, I also rewrote code that used
window.onpushstateto instead ofwindow.addEventListener('pushstate'), plus also added code to ensure we do not emit history changes multiple times, which may be possible (?).This is on v9 branch.