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
Would rotate such that the bottom list element would be on the bottom of the screen, just as if they had scrolled to the bottom entirely in portrait mode.
Actual Behavior
The bottom message ends up in the middle of the screen, with the remainder below it just being empty space. React native will re-render the list correctly if it is dragged, but not tapped.
This is iOS exclusive, on Android it exhibits expected behavior.
The snack UI does not allow for rotation as far as I know, so to see the bug create a new Project with 'react-native init RotationBug', copy paste that code into index.ios.js, and run with react-native run-ios.
The text was updated successfully, but these errors were encountered:
Is this a bug report?
Yes
Have you read the Bugs section of the How to Contribute guide?
Yes
Environment
react-native -v
:react-native-cli: 2.0.1
react-native: 0.47.1
node -v
:v6.11.0
npm -v
:5.3.0
Then, specify:
Target Platform: iOS
Development Operating System: macOS 10.12.5
Build tools: No native code, built using react-native run-ios
Steps to Reproduce
(Write your steps here:)
Expected Behavior
Would rotate such that the bottom list element would be on the bottom of the screen, just as if they had scrolled to the bottom entirely in portrait mode.
Actual Behavior
The bottom message ends up in the middle of the screen, with the remainder below it just being empty space. React native will re-render the list correctly if it is dragged, but not tapped.
This is iOS exclusive, on Android it exhibits expected behavior.
Reproducible Demo
https://snack.expo.io/B1P9GYJwb
The snack UI does not allow for rotation as far as I know, so to see the bug create a new Project with 'react-native init RotationBug', copy paste that code into index.ios.js, and run with react-native run-ios.
The text was updated successfully, but these errors were encountered: