Fixed
Status Update
Comments
il...@google.com <il...@google.com>
to...@yahoo.com <to...@yahoo.com> #2
Please include a sample project that reproduces your issue.
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?
jb...@google.com <jb...@google.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
Description
Component used: Fragment
Version used: 1.3.0-beta01
Devices/Android versions reproduced on: Pixel 2 API 29 emulator
Muzei's
main
module usesTRANSIT_FADE
to swap between fragments based on whether Muzei is your current wallpaper. This listener is set on aFlow
that runs when the fragment is at leastSTARTED
, meaning that callbacks end up normally being triggered as part of the move toSTARTED
.Reproduction steps:
FragmentManager.enableNewStateManager(false)
inMuzeiApplication
in themain
moduleExpected behavior: Next screen (
TutorialFragment
) appearsActual behavior: New fragment does not appear, despite going to
RESUMED
stateAdditional information: If I attach the layout inspector, the fragment magically appears!
Removing the
TRANSIT_FADE
or using the old state manager causes everything to work as expected as well.