Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Please include a sample project that reproduces your issue.
ta...@gmail.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?
il...@google.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
Version used: 1.1.0-alpha05
FragmentFactory has the method
public Fragment instantiate(@NonNull ClassLoader classLoader, @NonNull String className, @Nullable Bundle args)
but that method doesn't call setArguments(). While the Javadoc specifically calls this out, it is still confusing. The stated use case of constructing a different Fragment based on the arguments doesn't make much sense since developers can all setArguments() at any point after the fact (so needing a separate class for different arguments breaks down).