Please support nesting scrollable's in compose [241545426]

Assigned

Feature Request

compose-roadmap-proposal

Status Update

No update yet.

Description

xm...@gmail.com

created issue #1

Aug 6, 2022 04:08AM

Compose do not allow nesting of scrollable's in the same direction. But I have use case where layout consist of multiple sections. Each section can be a list, a grid, regular text etc... The entire layout is scrollable.

Recyclerview supports having multiple view types ( e.g. where a view can be another recyclerview which is a grid based)

But in compose, if you use a lazycolumn so that the entire layout is scrollable, you no longer can use LazyHorizontalGrid and LazyVerticalGrid inside it. You have to build your grid using a column

Any idea on how to get around this?

Comments

va...@google.com <va...@google.com> #2Aug 22, 2022 10:55PM

Hello, can you please attach a sample that reproduces your error?

lo...@gmail.com <lo...@gmail.com> #3Jul 19, 2024 01:34PM

I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally, https://gist.github.com/yatiksihag01/20106aa4855bd438e3eb982034d4bb7d is link to a GitHub Gist containing the code for my remote mediator file for your reference.

ch...@google.com <ch...@google.com> #4Jul 31, 2024 06:37PM

Based on first_launch_after_installation.mp4, your paging state is indeed showing null for nextKey, so it makes sense that Paging concluded there are no more items to load.

So I think the question is why the PagingState contains only an empty page and null values. My guess is either

RemoteMediator REFRESH actually returned empty data - what is the returned allNewsItems value on initial REFRESH?
RemoteMediator REFRESH successfully loaded data and inserted it into database, but Paging hasn't processed that yet by the time Append is triggered, so PagingState is empty.

The second case doesn't seem likely though.

If you attach an executable app, I can look into this further.

Otherwise, you may gain more insight through Paging logs with adb shell setprop log.tag.Paging VERBOSE. You can also try implementing RemoteKeys in this codelab which addresses possible races between Refresh and subsequent loads.

Message last modified on Jul 31, 2024 06:44PM

ag...@wayfair.com <ag...@wayfair.com> #5Oct 3, 2024 03:43PM

Hey! I ran into this same issue. It is in fact the second case you mentioned and is documented here.

I've published a repo reproducing the issue and filed a ticket proposing how this could be changed.

Message last modified on Oct 3, 2024 03:44PM

va...@gmail.com <va...@gmail.com> #6Oct 11, 2024 01:06PM

there are like thousands of cases where we need nested scrolling, in app development or UI design, implementing nested scrolling is a common requirement. Nested scrolling allows for smooth user interactions when there are multiple scrollable containers within each other, such as a grid or a list inside another scrollable container. Writing custom loops to handle these grids or nested lists just to achieve nested scrolling can complicate the codebase and reduce efficiency. Instead, developers can utilize pre-built solutions or frameworks that handle nested scrolling automatically, reducing both complexity and potential errors.

Issue 241545426