fix: hashchange should only be triggered for same page navigations #3768
+41
−30
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.
reverts parts of f6bd99e...49ea062
The original implementation by zonemeen was correct - 59e1773
hashchange
should not be triggered when navigating between different pagesThis PR also adds
hash
property inuseData
output for those who want to watch for hash change while navigating between pages - say from/foo#bar
to/
. Those who don't want this should stick withwindow.addEventListener('hashchange', ...)
It also emits correct event instance with
oldURL
andnewURL
forhashchange
now.