Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Please include a sample project that reproduces your issue.
jb...@google.com
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?
pa...@gmail.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
Component used: Fragment
Version used: 1.3.0
Devices/Android versions reproduced on: Android Studio Emulator with Android 11
I found a bug that requires the use of the Fragment library from 1.3.0 and up (I still reproduce the bug in the version 1.4.0-alpha06), custom animations in FragmentTransactions and a RecyclerView (of androidx.recyclerview:recyclerview:1.2.1).
If a fragment over which the soft keyboard is shown (because an EditText is focused for example), is replaced with a new fragment that shows a RecyclerView, and custom animations are set in the FragmentTransaction, then the soft keyboard is not automatically dismissed and is displayed over the second fragment. If the second fragment does not show a RecyclerView, or custom animations are not set in the FragmentTransaction, then the soft keyboard is automatically dismissed.
It is a regression since the soft keyboard was dismissed correctly when using a version of the Fragment library below 1.3.0.
I suspect that the issue comes from the new fragment state manager since I could not reproduce the issue when disabling it with the method:
I attached a screen recording of the issue captured on a Samsung Galaxy Tab s7, and a sample project.