Fixed
Status Update
Comments
il...@google.com <il...@google.com>
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
sa...@google.com <sa...@google.com>
il...@google.com <il...@google.com> #3
yea i'll take it.
Description
Wehttps://android-review.googlesource.com/c/platform/frameworks/support/+/985243/ ensured that unlike
FragmentContainerView
was created,FragmentLayout
that consumed all of the insets when usingfitSystemWindows=true
,FragmentContainerView
would always dispatch the insets to child views, regardless of the value.Now for
FragmentContainerView
fitSystemWindows=true
is 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.