Skip to content
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

Android SafeArea does not take into account the on-screen navigation buttons #19119

Open
FrozDark opened this issue Dec 24, 2024 · 1 comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification

Comments

@FrozDark
Copy link

Current behavior

SafeArea insets doesn't work with on-screen navigation buttons and content goes behind

image

Expected behavior

Content inside visible bounds

How to reproduce it (as minimally and precisely as possible)

SafeAreaUnoIssue.zip

Workaround

Use fullscreen mode

Works on UWP/WinUI

Yes

Environment

Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

Uno.Sdk: 5.5.56

Affected platforms

Android

IDE

Visual Studio 2022

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

@FrozDark FrozDark added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification labels Dec 24, 2024
@FrozDark FrozDark changed the title SafeAre does not take into account the on-screen navigation buttons Android SafeAre does not take into account the on-screen navigation buttons Dec 24, 2024
@FrozDark FrozDark changed the title Android SafeAre does not take into account the on-screen navigation buttons Android SafeArea does not take into account the on-screen navigation buttons Dec 24, 2024
@FrozDark
Copy link
Author

Seems like it is an issue of ExtendedSplashScreen not reverting back the android theme correctly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

1 participant