Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
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
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().
ap...@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).
il...@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
Version used: 1.1.0-alpha07
Devices/Android versions reproduced on: AVD Pixel 3XL running API 28
**Description**
If I use the `RESUME_ONLY_CURRENT_FRAGMENT` flag, as in
```FragmentStatePagerAdapter(supportFragmentManager, RESUME_ONLY_CURRENT_FRAGMENT)```
then...
**Expected**
Only the currently visible Fragment should be brought to RESUMED state, the immediate neighboring Fragments should be capped at STARTED.
**Actual**
The current and neighboring fragments are always `resumed`, then `paused`, then the current one is `resumed` again.
**Extra Info**
See screen recording that captures this behavior.