{{ message }}
test: add failing nested scroll restoration case - #98263
Open
aurorascharff wants to merge 1 commit into
Open
Conversation
Contributor
aurorascharff
marked this pull request as ready for review
September 4, 2026 12:45
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.

Summary
Adds an
it.failingregression test for a Cache Components scroll-restoration bug. A route-owned nested scroller restores on the first Back navigation, but after Forward and Back to the same retained route itsscrollTopresets to0.The fixture lives in the existing back/forward cache suite. Once the framework behavior is fixed, the witness test can be changed from
it.failingtoit.Reproduction: https://cache-components-nested-scroll-rest.vercel.app
Verification
HEADLESS=true pnpm test-dev-turbo test/e2e/app-dir/back-forward-cache/back-forward-cache.test.ts1000and received0when temporarily run withoutit.failing