Releases: AppAndFlow/react-native-safe-area-context
Releases · AppAndFlow/react-native-safe-area-context
v3.0.0
Breaking changes
- SafeAreaView insets are now relative to the nearest SafeAreaProvider. This brings the behaviour back to what it was in v1.0
- SafeAreaView prop
emulateUnlessSupported
has been removed.
Improvements
- SafeAreaView has a new
mode
prop to control if insets should be applied as padding or margin. (#85)
v2.0.3
v2.0.2
v2.0.1
v2.0.0
Breaking
- SafeAreaView padding is now additive to insets
- Native code changes, make sure to rebuild your app!
Improvements
- SafeAreaView is now implemented natively on both iOS and Android. Thanks to @jacobp100 (#78)
- Fix bottom inset when keyboard is opened on Android
v1.0.0
Breaking
- Insets on android are now relative to the Provider view instead of the activity content view. This is consistent with iOS.
SafeAreaContext
was renamed toSafeAreaInsetsContext
.
Deprecations
useSafeArea
is deprecated, useuseSafeAreaInsets
instead.SafeAreaConsumer
is deprecated, useSafeAreaInsetsContext.Consumer
instead.initialWindowSafeAreaInsets
is deprecated, useinitialWindowMetrics
instead.SafeAreaProvider
propinitialWindowSafeAreaInsets
is deprecated, useinitialMetrics
instead.
New
useSafeAreaFrame
hook andSafeAreaFrameContext
to access the frame of the nearestSafeAreaProvider
.withSafeAreaInsets
HOC
Fixed
- Insets should be more accurate on devices using API < 20