fix(client): No onAfterRouteChanged called after popstate #3227
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.
This Pull Request Fix issue #3226: No onAfterRouteChanged called after popstate
In
src/client/app/router.tspopstate eventListener, it should callonAfterRouteChangedhook afterloadPage,but it is missing.
... window.addEventListener('popstate', (e) => { loadPage( normalizeHref(location.href), (e.state && e.state.scrollPosition) || 0 - ) + ).then(() => { + router.onAfterRouteChanged?.(location.href) + }) }) ...Before Fix:

After Fix:
