Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
The default fling behavior of the horizontal pager sets the snapPositionalThreshold to 0.5. However, in normal cases, we don’t need to scroll beyond half of the screen since the fling behavior calculates the final snapping bound based on flingVelocity. However, when scrolling from a nested pager to a nearby page, DefaultPagerNestedScrollConnection always returns a velocity of zero. As a result, we are forced to scroll beyond half of the screen to reach the next page.
In my case, I choose to return the unconsumed velocity. Additionally, as DefaultPagerNestedScrollConnection is a private class, I have to do something like this.
So I can use it like
I believe there might be a better solution, and I hope this issue can be resolved in future updates.