Fixed
Status Update
No update yet.
Comments
il...@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).
il...@google.com
ap...@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().
jb...@google.com
Should clarify that if I filter out setCurrentPlayTime(0) (or replace it with setCurrentPlayTime(1)) it works well.
Also even with setCurrentPlayTime(0), onAnimationEnd is notified with correct delay (as if the animation has played).
jb...@google.com
@
I think that is intended for Animator. If you set the currentPlayTime to 0 or the total duration the animator completes. We do some
Description
Component used: Fragment Version used: 1.3.0-beta01
FragmentContainerViewoverridesonApplyWindowInsetsand dispatches fresh copy ofWindowInsetsto all children correctly. But it does not consumeWindowInsetsand being aViewGroupit then dispatches the insets again from theViewGroup.dispatchApplyWindowInsets. As a result the insets are dispatched second time toFragmentContainerViewchildren, but this time incorrectly - e.g. if first child consumes system window insets, other children receive empty window insets.