Spotify playback control bar position issue (When Desktop mode is OFF)
Categories
(Firefox for Android :: Browser Engine, defect)
Tracking
()
People
(Reporter: hyeondug.yeo, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
Steps to reproduce
- Go to Spotify site
- Desktop mode ON
- Sign in
- Select a song to play
- Find the playback control bar
Expected behavior
Spotify should always have a fixed position for playback control bar (same as when Desktop mode is Off)
Actual behavior
Spotify's playback control bar is inconvenient to use because it requires scrolling all the way to the bottom of the song list.
Device information
- Firefox version: 130.0a1
- Android device model: tablet-like device with a resolution of 1920x1080 and a density of 240 (hdpi) that defaults to landscape mode.
- Android OS version: S OS
Any additional information?
Comment 1•8 months ago
|
||
The severity field is not set for this bug.
:gl, could you have a look please?
For more information, please visit BugBot documentation.
Comment 2•7 months ago
|
||
Comment 3•7 months ago
|
||
Comment 4•7 months ago
|
||
Comment 5•7 months ago
|
||
The image is attached for reference. Comparison is made in both Chrome and Firefox with Desktop site OFF
Updated•7 months ago
|
Comment 6•7 months ago
|
||
Severity and Priority are set based on this guide, which explains why I'm resetting them.
Comment 7•7 months ago
|
||
Dear Donal Meehan
Could you please help me with an update on the issue?
Updated•7 months ago
|
Comment 9•7 months ago
|
||
I've moved this to general since it likely shouldn't be in the Homepage component.
:boek Could you move it to the right component and/or triage for severity/priority
Updated•7 months ago
|
Comment 10•2 months ago
|
||
The title of this bug and the STR in comment 0 seem backwards, which one is it? (at a glance, on fenix, both work for me, but...)
Comment 11•17 hours ago
|
||
Comment 12•17 hours ago
|
||
I'm unable to reproduce on a pixel tablet. This might be a web compat issue. Please attach a video with the bug and more specific device information if it is still occurring.
Description
•