Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
Over to Ralston to take a look. I imagine with the new relocation logic it should be fixed?
il...@google.com
What is happening here is that the TextField does not know that it is in a scrollable container, and since the keyboard is going to hide the currently focused text, the text field calls View.requestRectangleOnScreen which causes the entire app to pan up, and that clips the top bar.
The Relocation APIs are experimental right now. It is not used in TextField as we are past the alpha stage and can only use stable APIs in TextField. So this bug can only be fixed post 1.0
ap...@google.com
This should be fixed by
I verified that this sample code now works when soft input mode is AdjustResize.
il...@google.com
We've reverted the above change in https://android-review.googlesource.com/954182 since it is no longer needed - we've fixed setMaxLifecycle() to work with and without setReorderingAllowed(true) in https://android-review.googlesource.com/954024
This will be available in the next release of Fragments.
This will be available in the next release of Fragments.
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.