agrosner
02/13/2023, 3:51 PMCoordinatorLayout
, 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
implementationagrosner
02/13/2023, 3:52 PMkenkyee
02/13/2023, 3:54 PMNestedScrollinParent3
implementation"
Sounds like the right thing to do.
Scrollable in a scrollable sounds like a super weird thing to do though...agrosner
02/13/2023, 4:29 PMAndroidViewHolder
which does nested scrolling interop too…so ill see if that works.agrosner
02/13/2023, 7:37 PMagrosner
02/13/2023, 7:51 PMkenkyee
02/13/2023, 7:55 PMagrosner
02/13/2023, 7:56 PMagrosner
02/13/2023, 7:56 PMagrosner
02/13/2023, 7:57 PM