[BUG] Weird scrolling behavior in queue list
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
The report is a gesture conflict in the queue list: holding a track to drag while tapping “Scroll to playing song” drops the hold or fails to scroll, worse at low refresh rate. Search the Android UI for the queue screen and that scroll action; inspect how list drag and programmatic scroll interact. Reproduce with the given steps. Done when scroll-to-current works while a drag is held, including below 60 fps. No files or tests are named in the issue.
Written by the indexing model from the issue text.
Description
Describe the bug
When I open the queue list, scroll down a bit and hold a song to slide it up fast by clicking "Scroll to playing song", instead of taking me to the now playing song, it just ignores the song i was holding. Sometimes, it does work but I need to click "Scroll to playing song" multiple times. I will attach a screen recording to explain it better.
To Reproduce
Steps to reproduce the behavior:
- Go to gramophone and open any song
- Click the queue button and scroll down
- Hold any song to drag it to under the currently playing song
- Click "Scroll to currently playing song"
- See the error
Expected behavior
When I click "Scroll top playing song" while holding another song, I expect it to actually scroll to to current song.
Screenrecording
https://t.me/c/2007202545/535567
Smartphone (please complete the following information):
- Device: OPPO A78 4G
- OS: ColorOS 15 / Android 15
- App Version: 1.0.17.d8b10ba
Additional context
I said before that it actually sometimes behaves how I want it to but only if my screen's refresh rate is above 60. As i was screenrecording, the fps was clearly below 60 so it didnt behave as intended. Instead, i lost the song i was trying to drag under the currently playing song.
- I will open one issue per bug, follow the issue format and will add
[BUG]to the start of my issue title, and I acknowledge that if I don't follow the format, my issue might get closed without further explanation.
- Dominant language
- Kotlin
- Stars
- 2.3k
- Forks
- 136
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FoedusProgramme/Gramophone
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
FoedusProgramme/Gramophone#1048 ·
-
need confirm
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
FoedusProgramme/Gramophone#1024 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 18/100
FoedusProgramme/Gramophone#1052 · 4 comments ·
-
need confirm
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FoedusProgramme/Gramophone#1051 · 2 comments ·
-
need confirm
Difficulty 3/5 1-2 days Newbie friendliness 45/100
FoedusProgramme/Gramophone#1050 ·
All issues in FoedusProgramme/Gramophone
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openai/openai-java#1337 ·
Maintainers usually reply within 1 day
-
enhancement impact:U1 P3 reach:R2 size:S
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
sentry-loop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
paritytech/trinity-user-agents#1890 ·
Maintainers usually reply within 1 day
-
android:core
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Kotlin/kotlinx-io#543 ·