[fragment-scroll] Enable new scroll handler by default#95378
Merged
Conversation
eps1lon
force-pushed
the
sebbie/scroll-handler-by-default
branch
from
cf434ff to
10c972f
Compare
Contributor
Stats cancelledCommit: 29e9afb |
Contributor
Tests PassedCommit: 29e9afb |
acdlite
approved these changes
Jul 6, 2026
eps1lon
force-pushed
the
sebbie/scroll-handler-by-default
branch
from
8d5bce9 to
29e9afb
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
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.
This enables the new scroll handler by default. We consider the changed behavior a bug fix.
Segments where their first, top level DOM element was focusable, are no longer focused on soft-navigation (e.g. in
<><button /><main></main></>thebuttonis no longer focused on soft-navigation). This matches default browser behavior on hard-navigation.experimental.appNewScrollhandleris kept during the preview period as an opt-out to unblock yourself. Please file an issue and ping me if the new behavior is undesired. We plan to remove the opt-out before 16.3.