Fixed
Status Update
No update yet.
Comments
pr...@google.com
ap...@google.com
I was able to repro locally using the snippet in #1. The slide should never be applied to the content for state == 0, i.e. the green box.
Will take a look. Thanks for the repro steps, Jeremy.
jb...@google.com
ap...@google.com
I'm having an issue with Compose navigation-animation which might be caused by this.
I have two screens: List and Details.
List screen uses default transitions.
Details screen uses the following transitions:
enterTransition = {
slideIntoContainer(
AnimatedContentScope.SlideDirection.Up,
animationSpec = tween(400)
)
},
popExitTransition = {
slideOutOfContainer(
AnimatedContentScope.SlideDirection.Down,
animationSpec = tween(200)
)
},
The video is showing the bug vs expected. It's hard to describe: after clicking the back button before the transition to the Details screen was completed, the List screen moves up a little.
Description
Component used: Navigation
Version used: 2.9.0-alpha06
As of Navigation 2.9.0-alpha05, Navigation artifacts have started shipping KMP artifacts.
It would be helpful if the
navigation-testingartifact was also moved to KMP and used the new SavedState KMP APIs in SavedState 1.3.That would allow APIs like the
SavedStateHandle()factorySavedStateHandlefrom a@Serializableclass to be able to be used injvmTest, avoiding the need of using Robolectric or an Android device at all.