Fix: prevent incorrect page calculation when calling next() or scrollTo() after left overscroll at first page #839
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.
Description
Fixed edge case where left overscroll at first page with
loop=false
would cause incorrect page calculation when subsequently callingnext()
orscrollTo()
methods. The fix ensures proper page index handling during boundary overscroll scenarios.Changes:
Review
The changes maintain all existing library behaviors while fixing the overscroll edge case
Testing
Manual testing performed:
Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-08-20.at.11.32.55.mp4