You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On an iPhone, the big buttons for playing/skipping block the transcoding selector UI. Only certain qualities can be selected as a result, and scrolling through the list is difficult.
To Reproduce
Steps to reproduce the behavior:
On an iPhone, open any scene in Stash in Safari/Firefox
Click on the gear to bring up the quality selection UI
Notice that the big skip button blocks selecting most transcoding qualities
Expected behavior
User should be able to select any quality available. This should be able to be fixed by having the quality selection pop-up box be in front of the big playback buttons.
Screenshots
Stash Version: (from Settings -> About):
v0.22.1
Smartphone (please complete the following information):
Device: iPhone 12 Pro
OS: iOS 16.6
Browser: Safari/Firefox
Version: N/A
The text was updated successfully, but these errors were encountered:
Small CSS change to allow the `source-selector` to be brought to the front of the controls to allow people to select which source they would like.
At first, I was going more complex. I created functions that would disable the `big-buttons` if a menu was open and I got it mostly working but I felt like it was overkill when we can modify like 3-4 lines of CSS and get the same result.
fixesstashapp#4066
Describe the bug
On an iPhone, the big buttons for playing/skipping block the transcoding selector UI. Only certain qualities can be selected as a result, and scrolling through the list is difficult.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User should be able to select any quality available. This should be able to be fixed by having the quality selection pop-up box be in front of the big playback buttons.
Screenshots

Stash Version: (from Settings -> About):
v0.22.1
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: