forked from vfsfitvnm/ViMusic
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Formatting Issue in Top List Since Introduction of Bottom Nav Bar #1457
Comments
in 0.6.30 it's improved |
ok |
As far as I can see, the formatting issues still exists in all playlists. |
Fixed, available from version 0.6.31 |
Very good. Have you also considered other parts of the app that could potentially be obscured by the bottom bar? For example, this bug didn't just affect one playlist. |
Yes, consistent with the time I have. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce the bug
Navigate to the top list.
Observe the formatting of the top tracks list.
Note that the bottom navigation bar now obscures the last track in the list.
Expected behavior
The top list should display all tracks in full without any portion being obscured by the bottom navigation bar. The entire list, including the last track, should be visible and accessible to the user.
Actual behavior
Since the introduction of the bottom navigation bar, the last track in the top list is fully obscured by the bar. As a result, the user is unable to view or access the last track, leading to a discrepancy where for example the top 50 list now consists of only 49 tracks instead of the expected 50. This issue is particularly noticeable in the top list because it is numerically ordered, highlighting the absence of the last track.
Screenshots/Screen recordings
RiMusic version
0.6.29
Android version
Android 13
Additional information
Similar issues may exist with other playlists, although they are less noticeable due to their lack of numbering.
The text was updated successfully, but these errors were encountered: