Fixed
Status Update
No update yet.
Comments
sa...@google.com
Comment has been deleted.
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?
sa...@google.com
sr...@gmail.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
The
FragmentManagershould be converted over to saving its state using theSavedStateRegistryarchitecture component.We should provide
FragmentManagerwith aSavedStateRegistryControllerand move all of the code from theFragmentActivity'sinit()into theattachController()method ofFragmentManager.It currently relies on the
SavedStateRegistryof theFragmentActivitywhich hacked together methods likemarkFragmentsCreated()andmFragments.saveAllState()that can likely be called directly from theFragmentManager.The more complex piece is moving the
OnContextAvailableListener()over sinceFragmentManagerdoes not have the same signal for when theContextis immediately available.