Repository navigation
fix(docs): update FAQ on Chrome's scroll-to-top behavior - #266
Merged
Merged
Conversation
Recent Chrome versions (153+) scroll to the top after an intercepted push/replace navigation as the Navigation API spec requires, while Safari and older Chrome versions (e.g. 141) keep the previous scroll position. Update the FAQ and the docs site comment accordingly, and note that the workaround is harmless where the spec is followed. Closes #259 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UAz1tssRXbeyChnrheXK4Z
Bisecting Chrome for Testing builds against the WebKit bug 304593
repro shows Chrome 148 keeps the scroll position while 149 scrolls to
top. The fix is Chromium commit d6d5d3b9edd9 ("Scroll to top on
navigation.scroll() to a non-existent fragment", crbug.com/479874917),
first shipped in 149.0.7794.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UAz1tssRXbeyChnrheXK4Z
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
2 participants
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.
Closes #259
Summary
The "Browser doesn't scroll to top after navigation" FAQ said Chrome doesn't follow the Navigation API's automatic scroll-to-top behavior. Chrome has followed it since version 149.
FaqPage.tsx): now says Chrome follows the spec since version 149, while Safari and Chrome 148 and earlier keep the previous scroll position. Also notes that the workaround is harmless in browsers that follow the spec, since the page is already at the top.ClientApp.tsx): updated to match.The workaround code itself is unchanged. Safari and Chrome ≤148 still need it, and it does nothing in browsers that already scroll to top.
Which Chrome version fixed it
Chrome 149. The fix is Chromium commit
d6d5d3b9edd9, "Scroll to top on navigation.scroll() to a non-existent fragment" (crbug.com/479874917). It landed on 2026-04-14 and changesNavigateEvent::ProcessScrollBehavior()to scroll to the top when the destination URL has no matching fragment. That path is also used by the defaultscroll: "after-transition"behavior. It is not behind a flag. According to ChromiumDash, it first shipped in canary149.0.7794.0and reached stable in149.0.7827.22.Verification
Ran the WebKit bug 304593 repro page (scroll down, then do an intercepted
navigation.navigate("page2")) against official Chrome for Testing builds:The first fixed canary from the bisect,
149.0.7794.0, is the same build ChromiumDash lists for the commit.pnpm format:check,pnpm lint, and the docs package typecheck pass.🤖 Generated with Claude Code
https://claude.ai/code/session_01UAz1tssRXbeyChnrheXK4Z