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
{{ message }}
Repository navigation
Commit f2a8a05
Browse filesBrowse the repository at this point in the historyBrowse files
Render the internal SafeAreaView from the safe area insets prop
The core surfaces that cannot depend on `react-native-safe-area-context` —
LogBox, the element inspector, `InputAccessoryView` — get their safe area
padding from a private component that until now wrapped the native
`RCTSafeAreaView`. It applies the prop instead, in JavaScript.
The insets come from the synchronous inset event, which is processed in the
frame that mounts the view, so the first frame is already padded.
Two consequences, both visible in the updated LogBox snapshots: these
surfaces now apply safe area padding on Android too, where they previously
fell back to a plain `View`, and they re-render when insets arrive rather
than being padded natively.
The native implementations are untouched here — the deprecated public
`SafeAreaView` still uses them. This only moves the internal component onto
the prop, so the two can be compared against each other before the native
side is removed.
0 commit comments