Fixed
Status Update
No update yet.
Comments
il...@google.com
jb...@google.com
ap...@google.com
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
sa...@google.com
il...@google.com
I have a similar issue with plain AnimatorSet:
set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()
doesn't play animation in resume().
Description
Wehttps://android-review.googlesource.com/c/platform/frameworks/support/+/985243/ ensured that unlike
FragmentContainerViewwas created,FragmentLayoutthat consumed all of the insets when usingfitSystemWindows=true,FragmentContainerViewwould always dispatch the insets to child views, regardless of the value.Now for
FragmentContainerViewfitSystemWindows=trueis a no-op, but we should instead throw an error and indicate to the user that if they would like to handle insets they should do so at each individual fragment view.