Genymobile / Genymobile/scrcpy
Compose LazyColumn not scrollable
- Dominant language
- C
- Stars
- 150k
- Forks
- 13.7k
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 2
Description
- scrcpy version: v1.18
Tracking issue from this StackOverflow post: https://stackoverflow.com/questions/68954790/why-is-lazycolumn-not-scrollable-using-mouse-but-recycler-view-is
> I am using scrcpy to mirror and control my physical test mobile device using my desktop.
>
> I am migrating an app from views to jetpack compose.
> This is something I observed and I am curious why this happens so.
>
> Using the desktop mouse scroll wheel, I am able to scroll a RecyclerView.
>
> But I am not able to do so in a LazyColumn.
>
> Note: I am able to scroll the LazyColumn using the mouse by click and drag.
> Only the scroll wheel is not working.
https://stackoverflow.com/questions/68954790/why-is-lazycolumn-not-scrollable-using-mouse-but-recycler-view-is/68964204#comment121884201_68964204
> I have not tried with OTG as I don't have one. In case you missed it, on the same desktop using `scrcpy` I am able to scroll the app when it had recycler view. The issue is when using compose `LazyColumn`. But I tried an alternative of `scrcpy` and that scrolls both recycler view and compose `LazyColumn`.
Minimal sample to reproduce: https://github.com/Abhimanyu14/compose-scroll
EDIT: oops, I missed the initial issue #2598. I keep this one because the discussions are there.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the mouse-wheel behavior with the linked compose-scroll minimal sample on scrcpy v1.18, comparing LazyColumn with RecyclerView. Read the discussion in issue #2598 and the linked StackOverflow report before investigating further. Done means the mouse wheel scrolls the Compose LazyColumn as expected, but this issue appears to have moved to #2598.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- desktop, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100