Status Update
No update yet.
Comments
an...@sigma.software
I'm marking this as "won't fix" as there's nothing Compose here can do, as this is a platform quirk that has been adjusted to be more predictable in recent API versions.
The crux of the issue here is the fitSystemWindows in the extra View, like you mentioned, and a platform change in API 30.
Prior to API 30, window insets were dispatched through the view hierarchy in a non-intuitive way: Rather than being a full breadth-first traversal, they would be dispatched in preorder. If the insets were consumed at any point (like if you use fitSystemWindows), then the preorder would prevent insets from being dispatched to the rest of the view hierarchy. This is very unintuitive: It meant that sibling views (or views deeper in the tree) could stop later views from receiving the dispatch of insets.
In API 30, this behavior was changed to be more intuitive: Now, insets are dispatched in a top-down manner, so they can't be consumed in this weird, cross-tree way.
There's a couple solutions here:
- Avoid
fitSystemWindowsfrom views if you're handling insets manually - Override
dispatchApplyWindowInsetsin the view groups above where you havefitSystemWindowsdefined, and manually perform the new, non-broken dispatching behavior. You can see a comparison of the two methods here:https://cs.android.com/android/platform/superproject/+/master:frameworks/base/core/java/android/view/ViewGroup.java;l=7341-7371;drc=6411c81462e3594c38a1be5d7c27d67294139ab8
tr...@gmail.com
Using composable version 1.2.1, I could fix it using:
override fun onCreate(bundle: Bundle?) {
WindowCompat.setDecorFitsSystemWindows(window, false)
super.onCreate(bundle)
if (Build.VERSION.SDK_INT > Build.VERSION_CODES.Q){
window.setFlags(WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS, WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS)
}
}
Then statusBarsPadding works as expected on Api 29
Description
There is no visual issue when using Material transitions in fragments instead of Animators.
Fragment transitions are extremely inflexible comparing to navigation action animations. Same fragment may be used in different navigation actions with different animations, making transition configuration extremely clumsy or even impossible in some scenarios. The simplest example is multiple back stack with bottom navigation: bottom tab fragments must support different animations for 1) navigating to a different tab 2) navigating to 'inner' screen (shared axis X). I haven't found any stable solution of how to implement this with fragment transitions.
There is a little information out there about predictive back navigation with fragments, so I'm also looking for explanation on material transitions with navigation - is there any easy way to replace action animations with transitions, in other words customizing fragment transitions of two different fragments when performing navigation action?
Component used: Navigation
Version used: 2.8.4
Devices/Android versions reproduced on: Multiple emulators / Android API 35
Sample project:
Sample video attached.