Fixed
Status Update
No update yet.
Comments
da...@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).
Description
Version used: fragment-ktx:1.3.0-beta01
This bug is part of the problem of
Steps to reproduce
- Fragment1 replaced with fragment2, then press BACK as soon as I see the fragment2 is showing.
- Upon returning, fragment1 calls AnimationInfo.mFocusedView.requestFocus(). However the view being called requestFocus() belongs to the old view tree, it's not belonging to the new view tree that is created during returning.
The bug is hard to reproduce. It's around 1/50 for me using project at
Attached a screenshot showing "detached state" of the view.
The bug is probably not critical because calling requestFocus() on a detached view should be no-op. But it may cause problem if the app added a onFocusChange listener and perform some logic in the fragment (as illustrated in leanback crash