Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Please include a sample project that reproduces your issue.
ap...@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?
jb...@google.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
There are no use cases when we should allow a fragment's Lifecycle to be moved to
DESTROYEDother than when the fragment is actually destroyed.Therefore, you should not be able to
setMaxLifecycle()toDESTROYEDthrough aFragmentTransaction, initialize aFragmentScenariowithDESTROYED, or move aFragmentScenarioto theDESTROYEDstate usingmoveToState().Doing any of these things should throw an error.