Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
Please include a sample project that reproduces your issue.
il...@google.com <il...@google.com>
ap...@google.com <ap...@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?
il...@google.com <il...@google.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
Description
Version used: 1.1.0-alpha09
Devices/Android versions reproduced on:
When using nested fragments such as:
Parent
-- Child
I'd expect the Lifecycle changes of these fragments to be properly nested:
Parent CREATED
Child CREATED
Parent STARTED
Child STARTED
Parent RESUMED
Child RESUMED
---
Child PAUSED
Parent PAUSED
Child STOPPED
Parent STOPPED
Child DESTROYED
Parent DESTROYED
But I'm not seeing that - it seems like the opposite is the case - the child gets changed first on the way up and after on the way down, perfectly *not* nesting.