Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
Please include a sample project that reproduces your issue.
jb...@google.com <jb...@google.com> #3
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?
an...@google.com <an...@google.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
Description
Version used: 1.2.0-rc05
When called on a view within a fragment added with a <fragment> tag in a layout, FragmentManager.findFragment(view) returns either the containing fragment's parent, or crashes as it can not find any parent fragment.
I've attached a sample project which crashes on startup due to the bug. Replacing the <fragment> tag with FragmentContainerView or a framelayout with a manual transaction avoids the crash