fix: scroll to top when navigating between pages - #3237
Open
singhvishalkr wants to merge 1 commit into
Open
Conversation
When clicking prev/next links or sidebar navigation, the page now scrolls to the top instead of preserving the scroll position from the previous page. This uses to ensure scrolling happens after the DOM updates. Fixes vuejs#2156
singhvishalkr
force-pushed
the
fix/scroll-to-top-on-page-change
branch
from
May 25, 2026 17:13
61d49cf to
11570ba
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
1 participant
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.
I noticed that navigating between pages via the prev/next buttons or sidebar links keeps the scroll position from the previous page, which is disorienting. For example, scrolling to the bottom of one page and clicking "Getting Started" in the footer lands you at the bottom of the new page instead of the top.
The router's built-in scrollBehavior returns
{ x: 0, y: 0 }but doesn't always fire correctly with async page components. I added explicit scroll handling in the Layout's afterEach hook - it checks if the path actually changed (ignoring hash-only navigation) and scrolls to top after the DOM updates via $nextTick.Tested locally by clicking through the sidebar and prev/next navigation - pages now consistently start from the top.
Fixes #2156