Fixed
Status Update
Comments
jb...@google.com <jb...@google.com> #2
Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.
ya...@google.com <ya...@google.com> #3
Great! Thanks a lot, I'll look for the live updates soon!
jb...@google.com <jb...@google.com> #4
This has been fixed internally and will be available in the Fragment 1.2.0-beta01 release. We use whatever the default behavior of a FrameLayout is and allow that in API levels below 18.
https://b.corp.google.com/issues/141657641 was created to explore solutions that will no longer need to call setLayoutTransitions() on the Fragment view's parent for transitions to work appropriately.
Description
Version used: 1.2.0-alpha01
Devices/Android versions reproduced on: API level 17 and below
androidx.transition needs setLayoutTransition for suppressing layouts during Fragment Transitions
FragmentContainerView was added in this CL. It disables setLayoutTransition.
However, androidx.transition uses setLayoutTransition to simulate the behavior of setSuppressLayout on API levels 17 and below.
RecyclerView had the same issue, and this CL fixed it.
This issue was originally reported here: