We have a bunch of legacy fragment screens with a
CoordinatorLayout
, where we have an inner composable fragment contained inside of that. What happens is that the
CoordinatorLayout
gives the content size a bunch of extra height below the visible, scrollable size of a compose
LazyVerticalGrid
. We’ve turned on the nested scrolling interop, but the coordinator layout is two levels up, so overridding the
LocalView.current
feels wrong. Also, a compose fragment can appear in other composable hierarchies if the content hierarchy above the composable shifts, it will break again.
Anyone have a good solve for this? Im thinking of walking up the parent tree to find the nearest coordinatorlayout or wrapping the composeview in a
NestedScrollinParent3
implementation