Fixed
Status Update
No update yet.
Comments
ap...@google.com
Please include a sample project that reproduces your issue.
jb...@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?
Description
Component used: Fragment Version used: 1.3.0-alpha06
Right now,
setMaxLifecycle()only supportsLifecycle.State.CREATEDor higher. It would be nice ifsetMaxLifecycle()could also supportLifecycle.State.INITIALIZINGonly for Fragments that have never moved aboveCREATED- i.e., only something that could be set alongside the Fragment being added to theFragmentManager.This would allow developers and libraries built on top of fragments to keep fragments only at the attached state without going through
onCreate().