Fixed
Status Update
No update yet.
Comments
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.
ad...@gmail.com
ma...@gmail.com
Hello, any update please?
Description
When using the
<fragment>tag orFragmentContainerViewIn the case of the
<fragment>tag:VIEW_CREATEDand never makes it any furtherfor
FragmentContainerView:RESUMEDthe first time, but on configuration change, the view that inflates the fragment is never attached to the new view hierarchy, so the fragment isRESUMEDbut never actually visible.We should address this issue for both components.
<fragment>tag case. This bug will track theFragmentContainerViewcase.