Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
However, during predictive back animation the entering screen is drawn on top of the exiting screen as the video linked in the issue also reproduces
navigation library used: 2.8.0-alpha06
[Deleted User] <[Deleted User]>
It looks like a possible root cause could be that the exiting destination is correctly drawn on top when there's a pop, but predictive back press isn't actually pop and therefore isn't drawn on top.
Most of the logic seems to check composeNavigator.isPop.value || inPredictiveBack, but targetZIndex only checks pop when it should instead probably check for either pop or inPredictiveBack?
jb...@google.com
Once a sample project is provided we will reopen this issue, as we cannot reproduce this at the moment.
[Deleted User] <[Deleted User]>
I have created a sample project which reproduces the issue, and attached a video.
When enableOnBackInvokedCallback is enabled in manifest, the pop exiting destination is incorrectly drawn underneath the pop entering destination. When it is disabled, everything works as expected (but no predictive back)
Description
Component used: Navigation Version used: 2.8.0-alpha04 Devices/Android versions reproduced on:
The goal is to make sure that the incoming screen appears from behind the current screen (instead of on top of the current screen as shown in the video) when implementing predictive back animation.
The following is the configuration used to produce the attached video. Couldn't find transition that deals with zIndex.