You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using sliding animations, specifically slideOutDown, the animation's Y-axis trajectory does not adjust according to the orientation change.
Detailed Description
Initialization: The app is initialized in landscape mode, and the slideOutDown animation works as expected, fully sliding the element off the screen. Orientation Change: After the device switches to portrait mode, when the slideOutDown animation is triggered again, the animation ends at a position in the lower middle of the screen, rather than completely sliding out of the screen.
Steps to Reproduce
Start the app in landscape mode.
Trigger the slideOutDown animation and observe the behavior.
Rotate the device to portrait mode.
Trigger the slideOutDown animation again and notice the ending position.
Expected Behavior
The slideOutDown animation should always finish with the element completely out of the screen, regardless of the device's orientation.
Problem Description
When using sliding animations, specifically slideOutDown, the animation's Y-axis trajectory does not adjust according to the orientation change.
Detailed Description
Initialization: The app is initialized in landscape mode, and the slideOutDown animation works as expected, fully sliding the element off the screen.
Orientation Change: After the device switches to portrait mode, when the slideOutDown animation is triggered again, the animation ends at a position in the lower middle of the screen, rather than completely sliding out of the screen.
Steps to Reproduce
Expected Behavior
The slideOutDown animation should always finish with the element completely out of the screen, regardless of the device's orientation.
Environment
react-native-animatable version: 1.3.3
React Native version: 0.70.6
Device details: any Android
The text was updated successfully, but these errors were encountered: