Fixed
Status Update
No update yet.
Comments
ap...@google.com
Please include a sample project that reproduces your issue.
il...@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?
to...@yahoo.com
Hello, have you checked sample project? I hope it will help find the issue.
gr...@gmail.com
to...@yahoo.com
Hello, any update please?
gr...@gmail.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?
Description
Now that the
MenuProviderinterface contains the optionalonPrepareMenu()API to maintain 1:1 compatibility, we want to make sure thatToolbar'sMenuHostHelperutilizes this API in case developers choose to implement it when adding aMenuProvider.