-
Notifications
You must be signed in to change notification settings - Fork 203
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
Volume bar opens to left of volume icon and covers the play buttons #351
Comments
Hello @giorgosioak, thanks for the suggestion and the usecase problem well detailed. I will try to find a nice solution to this problem :) |
Two quick mockups (poke @vprigent, @YurySolovyov). This is more what I had in mind. Just a few CSS tweaks. personal preference for the first one, what do you think? @vprigent Do you want to work on it? |
Still 1 more interaction (click/hover) than needed. |
One possibility I see is to rework header in a way that will allow us to place volume control below or above the playback controls |
One requirement that I have is: "in a 1920*1080 screen, Museeks minimum width should not exceed half of the screen width". Having a look at @giorgosioak problem, it's just he cannot adjust volume then directly click an play/pause. It's not really that he has to hover the volume to show |
@KeitIG Correct |
A bit unrelated, but it could be solved in the same issue. From #423 by @lottanbettan
|
Wow, I missed a lot of things here. A popup for the sound bar does not feel "good". |
#509 seems like a good solution. Why isn't this getting merged? |
The volume bar opens at the left of the volume icon and covers the play buttons until you move the mouse away. Sometimes you want to click pause you move your mouse over the volume icon and you need to make a second move to close the volume bar that pops up. Being on the right side of volume icon makes it more simple.
My suggestion is to make it open at the right of the icon 😉
Specs:
Museeks 0.8.1 (Installed via AUR) -- OS: Arch Linux -- Kernel: x86_64 Linux 4.11.7-1-ARCH
The text was updated successfully, but these errors were encountered: