Fixed
Status Update
No update yet.
Comments
il...@google.com
jb...@google.com
ap...@google.com
Please include a sample project that reproduces your issue.
sa...@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?
Description
Wehttps://android-review.googlesource.com/c/platform/frameworks/support/+/985243/ ensured that unlike
FragmentContainerViewwas created,FragmentLayoutthat consumed all of the insets when usingfitSystemWindows=true,FragmentContainerViewwould always dispatch the insets to child views, regardless of the value.Now for
FragmentContainerViewfitSystemWindows=trueis a no-op, but we should instead throw an error and indicate to the user that if they would like to handle insets they should do so at each individual fragment view.