Fixed
Status Update
No update yet.
Comments
yu...@google.com
Please include a sample project that reproduces your issue.
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?
ma...@gmail.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
It would be great if we can work around this bug somewhere in the support library so that app developers can easily avoid this issue just by updating the SDK and rebuild their apps.
Typical steps to reproduce this issue (if the app is suffering from
1. Launch the app.
2. Hit the back button on the NavBar.
3. Wait for a while.
Expected behavior:
InputMethodManager#mServedView and InputMethodManager#mNextServedView should be null.
Actual behavior:
InputMethodManager#mServedView and/or InputMethodManager#mNextServedView still holds a strong reference to View object.