Fixed
Status Update
No update yet.
Comments
jb...@google.com
ap...@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?
Description
When using FragmentStrictMode, it might not be possible or prudent to fix all violations at once.
It would be convenient to let developers build up their allow list of Fragment class name + Violation class name pairs that could serve as the baseline for their app.
This would allow developers to enable more strict penalties for new violations while slowly working down the set of known violations, effectively allowing them to stop the bleeding and avoid regressions as new features are developed.