Fixed
Status Update
Comments
il...@google.com <il...@google.com>
da...@gmail.com <da...@gmail.com> #2
Any updates?
ap...@google.com <ap...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-master-dev
commit e0e7d20aa718593fcc3be260f9cded0a6464ec28
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Dec 01 08:47:03 2020
Fix improper animations after pop
When combining pop and replace operations in the same fragment
transaction and using the new state manager, the fragment in the
transaction being popped does not have a view and therefore its
animation is ignored.
We should ensure we consider any animations that are available, even if
the fragment has no view.
RelNote: "Combining pop and replace operations in the same fragment
transaction will now show the proper animations"
Test: removingFragmentAnimationChange
Bug: 170328691
Change-Id: Ifd4e49cd9874a9ac0673083c27ef3c9765bbfa04
M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentAnimationTest.kt
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java
https://android-review.googlesource.com/1515043
Branch: androidx-master-dev
commit e0e7d20aa718593fcc3be260f9cded0a6464ec28
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Dec 01 08:47:03 2020
Fix improper animations after pop
When combining pop and replace operations in the same fragment
transaction and using the new state manager, the fragment in the
transaction being popped does not have a view and therefore its
animation is ignored.
We should ensure we consider any animations that are available, even if
the fragment has no view.
RelNote: "Combining pop and replace operations in the same fragment
transaction will now show the proper animations"
Test: removingFragmentAnimationChange
Bug: 170328691
Change-Id: Ifd4e49cd9874a9ac0673083c27ef3c9765bbfa04
M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentAnimationTest.kt
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java
jb...@google.com <jb...@google.com> #4
This has been fixed internally and will be available in the next Fragment release.
Description
Component used: Fragment Version used: 1.3.0-beta01
The videos attached show the behavior of the app when built using version 1.2.5 and 1.3.0-beta01.
I tried the SNAPSHOT (6890032) version, but the issue is still there.