Implement NativeSafeArea APIs to support forced edge-to-edge#46051
Closed
alanleedev wants to merge 1 commit into
Closed
Implement NativeSafeArea APIs to support forced edge-to-edge#46051alanleedev wants to merge 1 commit into
alanleedev wants to merge 1 commit into
Conversation
facebook-github-bot
added
CLA Signed
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D61293744 |
…6051) Summary: Pull Request resolved: react#46051 Changelog: [Internal] (added extension function to PixelUtil) With Android 15, apps built with `targetSdk` 35 will have edge-to-edge enforced. This means that content will be expanded to fill the whole screen and will be rendering below system bars like status bar and navigation bar. This change will add support to return proper inset values for apps running on Android 15 w/ targetSDK of 35. [SafeArea.js](https://www.internalfb.com/code/fbsource/xplat/js/RKJSModules/Libraries/SafeArea/specs/SafeArea.js) calls NativeSafeArea for the implementation. Non-goal: This is to just to support forced edge-to-edge for A15 in Meta internal apps and not intended as an general edge-to-edge support for OSS. Differential Revision: D61293744
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D61293744 |
alanleedev
force-pushed
the
export-D61293744
branch
from
ba71edc to
5d76e1c
Compare
Collaborator
|
This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
react-native-bot
added
Stale
Collaborator
|
This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
react-native-bot
added
Stale
Collaborator
|
Closing as this PR is no longer needed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
Changelog: [Internal]
(added extension function to PixelUtil)
With Android 15, apps built with
targetSdk35 will have edge-to-edge enforced.This means that content will be expanded to fill the whole screen and will be rendering below system bars like status bar and navigation bar.
This change will add support to return proper inset values for apps running on Android 15 w/ targetSDK of 35.
SafeArea.js calls NativeSafeArea for the implementation.
Non-goal: This is to just to support forced edge-to-edge for A15 in Meta internal apps and not intended as an general edge-to-edge support for OSS.
Differential Revision: D61293744