-
Notifications
You must be signed in to change notification settings - Fork 1.8k
SafeAreaView is not implemented #859
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
Comments
Are you saying that Safari doesn't prevent OS chrome from covering the web UI by default? |
No, it’s physical protrusions - such as the iPhone X “notch” - covering the UI. I can’t speak to what the situation is on Android devices that also have sensor housing screen cut outs, but I would expect them to require similar workarounds. Actually, it’s OS chrome as well. The iOS Home Indicator covers UI sometimes. |
This documentation claims otherwise:
|
Somewhat misleading. You can observe the issue with a minimal demo. Safari without Safari with You can see this conflict between app UI and browser chrome when viewing a Medium.com link in the Twitter in-app browser. The Open in App link is hidden by browser chrome until you scroll, and even then it's still partially underneath the home indicator. |
Do you want to request a feature or report a bug?
Request a feature
What is the current behavior?
SafeAreaView
is an alias ofView
If the current behavior is a bug, please provide the steps to reproduce and
if a minimal demo of the problem via Glitch or similar (template:
https://glitch.com/edit/#!/react-native-web-playground).
N/A
What is the expected behavior?
SafeAreaView would work on Web as it does on Native. That is, it would be possible to use it to prevent the sensor housing, home indicator, corners, etc. from occluding UI.
Environment (include versions). Did this work in previous versions?
I have a rough version of this that I built for my own use. I'm sure that it is not robust enough for inclusion in this project as is, but I would happy do the work to make it so given sufficient guidance.
The text was updated successfully, but these errors were encountered: