Fixed
Status Update
No update yet.
Comments
vi...@google.com
vi...@google.com
Please include a sample project that reproduces your issue.
[Deleted User] <[Deleted User]>
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?
vi...@google.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
I'm trying to confirm some threading assumptions in a codebase. It currently boils down to the following question:
Can I assume that Fragment.onViewCreated() and Fragment.onResume() are always called on the application's main thread?
As far as I can tell there is no reason for either to be called on a worker thread, but I'm worried my assumption might cause trouble in the future. I'd like to request the addition of "@MainThread" and/or "@AnyThread" to those methods to alleviate that uncertainty.