Fixed
Status Update
Comments
jb...@google.com <jb...@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?
Description
Component used:
Fragment
Version used:
1.3.0-beta01
Devices/Android versions reproduced on:
Google Pixel 4 XL
There are some key components here:
startPostponedEnterTransition
instantly after postponingThe effect is really noticeable when using the MDC transitions since they are currently not handling cancelations gracefully so it leaves the target view with alpha 0.
One fix is to always wait calling
startPostponedEnterTransition
at least one frame by posting to a handler or usingyield()
with Coroutines.You may wonder why I'm calling start instantly and it's because the data is cached: