Fix animation related issues and improve the swipe performance #149
Conversation
This file contains 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
…h a duration, divide into 2 parts. While swipe is in progress, we use 0 duration all the time and for the animations we use the provided or default value i.e. 400ms. This will also fix the swipe thumb frozen in the middle on real devices.
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.
Instead of every container width change goes through an animation with a duration, divide into 2 parts. While swipe is in progress, we use 0 duration all the time and for the animations we use the provided or default value i.e. 400ms. This will also fix the swipe thumb frozen in the middle on real devices.
Screen_recording_20250201_222801.mp4
Screen_recording_20250201_222917.mp4
Test Coverage