-
-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use 'SafeAreaView' through the app #3067
Commits on Sep 23, 2020
-
safeAreaView: Ensure
MainScreenWithTabs
is alignedMakes sure our main tabs are aligned properly with the edges of the screen on iOS. More about how safe areas work on iOS: https://developer.apple.com/documentation/uikit/uiview/positioning_content_relative_to_the_safe_area About the React Native-specific component: https://facebook.github.io/react-native/docs/safeareaview
Configuration menu - View commit details
-
Copy full SHA for 19f367a - Browse repository at this point
Copy the full SHA 19f367aView commit details -
screen: Use
SafeAreaView
in Screen componentInstead of using `react-native-safe-area` and getting the inset values from the `session` state, use `SafeAreaView` witch is a component coming with React Native.
Configuration menu - View commit details
-
Copy full SHA for deba961 - Browse repository at this point
Copy the full SHA deba961View commit details -
composebox: Use
SafeAreaView
in ComposeBoxFixes zulip#3066 Previous approach almost worked correctly, but there was one case it didn't - when the keyboard did pop on an iPhone, the bottom space was sill there, though it shouldn't, as the keyboard is located over the `Home Indicator`.
Configuration menu - View commit details
-
Copy full SHA for 3a01a26 - Browse repository at this point
Copy the full SHA 3a01a26View commit details -
Use
SafeAreaView
inChatScreen
All 'screen'-type components need a `SafeAreaView` to make sure the offsets from the edges are correct. This makes sure we do that fot the `ChatScreen` component.
Configuration menu - View commit details
-
Copy full SHA for 13f1ea8 - Browse repository at this point
Copy the full SHA 13f1ea8View commit details -
safeArea: Do not track safea area insets
We no longer need `react-native-safe-area` so stop using it to track the changes to the safe area insets (we are using `SafeAreaView`)
Configuration menu - View commit details
-
Copy full SHA for 57a52ca - Browse repository at this point
Copy the full SHA 57a52caView commit details -
Configuration menu - View commit details
-
Copy full SHA for 838136d - Browse repository at this point
Copy the full SHA 838136dView commit details -
sessionReducers: Remove
safeAreaInsets
We no longer track `safeAreaInsets` data so remove i from the reducer.
Configuration menu - View commit details
-
Copy full SHA for bb5d104 - Browse repository at this point
Copy the full SHA bb5d104View commit details -
cleanup: Remove actions and types about safe area insets
No longer used and needed. Remove completely from the codebase.
Configuration menu - View commit details
-
Copy full SHA for 4e9ad92 - Browse repository at this point
Copy the full SHA 4e9ad92View commit details -
cleanup: Remove 'react-native-safe-area'
Now, completely unused, remove the 'react-native-safe-area' package.
Configuration menu - View commit details
-
Copy full SHA for 90a39b3 - Browse repository at this point
Copy the full SHA 90a39b3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 96981eb - Browse repository at this point
Copy the full SHA 96981ebView commit details