Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
Please include a sample project that reproduces your issue.
il...@google.com <il...@google.com> #3
Here is the sample project.
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
ap...@google.com <ap...@google.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
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.