Fixed
Status Update
No update yet.
Comments
li...@gmail.com
Please include a sample project that reproduces your issue.
se...@google.com
il...@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?
ug...@gmail.com
Hello, have you checked sample project? I hope it will help find the issue.
bo...@gmail.com
il...@google.com
[Deleted User] <[Deleted User]>
Hello, any update please?
ra...@gtempaccount.com
Hello
I raised similar issue with this ticket
This makes the SearchView unusable/broken when fragments are changed (i.e base on searchView input query)
What can we do to fix this problem? What is the progress of work on solving this problem?
jo...@gmail.com
@7 Check @5 for a workaround.
jb...@google.com
ap...@google.com
Hi, i am also facing this issue after we dismiss a DialogFragment, the callback comes in the onPrepareOptionsMenu(), which is causing the issues for me.
Any idea on when it will be fixed?
Any idea on when it will be fixed?
Description
Version used: 1.0.0-alpha03
Devices/Android versions reproduced on: All
The attached sample project consists of three fragments: Step1, Step2, Step3
Step1 can navigate to two destinations (both are Step2 fragment).
Both Step2 destinations has an action to go to Step3. The destination with a problem action has popUpTo set to Step1.
All actions have the same transition animations set.
When tapping next on Step2 (on destination with navigation action with popUpTo=Step1) the Step2 fragment is being animated the wrong way.