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
This causes application and system UI overlaps in Avalonia where the Application was not previously designed as edge to edge.
One solution is to use InsetsManager.IsSystemBarVisible = false to hide the status and navigation bars, but in some cases I'd still like to retain them and keep using padding like in previous versions.
The article reads
If your app must offer custom background protection to 3-button navigation or the status bar, your app should place a composable or view behind the system bar using WindowInsets.Type#tappableElement() to get the 3-button navigation bar height or WindowInsets.Type#statusBars.
How does that translate to Avalonia terms? I was hoping maybe InsetsManager.SafeAreaPadding would be aware of the height of the status and navigation bars on Android 15, but it reports thickness of 0.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
https://developer.android.com/about/versions/15/behavior-changes-15#ux
This causes application and system UI overlaps in Avalonia where the Application was not previously designed as edge to edge.
One solution is to use
InsetsManager.IsSystemBarVisible = false
to hide the status and navigation bars, but in some cases I'd still like to retain them and keep using padding like in previous versions.The article reads
How does that translate to Avalonia terms? I was hoping maybe
InsetsManager.SafeAreaPadding
would be aware of the height of the status and navigation bars on Android 15, but it reports thickness of 0.Beta Was this translation helpful? Give feedback.
All reactions