Mute button for Pop-out Video – Vivaldi Browser snapshot 1964.3
-
This snapshot adds a mute button to the pop-out video (Picture-In-Picture [PiP]) window.
Click here to see the full blog post
-
First!
-
-
=
-
@pathduck: In English?
-
Do you mean this because if so it works for me
-
@Ruarí No, just trying (and apparently failing) to be funny
-
Hmm, I keep losing menu customisation for the Bookmarks menu on updates
Basically, the whole bookmarks list gets lost and I have to re-add it. -
Hi,
I'm hopeful that this snapshot hopefully address's this issue: https://forum.vivaldi.net/topic/48573/sites-don-t-work-blocking-and-now-lockups/2?_=1593517078286 -
Noice :3
-
Not specific to today's snapshot, but I just noticed that displaying the close button on the right moves the mute button/PiP button to the left, hiding the favicon. I gotta say, I'm not a fan of this (it's not even centered!). I might end up sticking with my css mod for a while longer, so I take back what I said a week ago.
-
@pathduck: Hey pat, could you make a bug on this and attach the mainmenu.json to the report? And try to be as clear as possible, as its not super clear what you mean here, thanks!
-
@Aronand I managed to repro in a clean standalone snapshot. Reported as VB-69398.
I've not tested in Stable.
-
VB-59319 is not fixed for not using native Window (there is no bar, but you can still double click an empty space in the tab bar and you see it try and fails to go full screen)
-
@Ruarí Mute button doesn’t seem to work on Gnome 3.36.3. The mouse pointer turns into a cursor of four arrows, which indicates it switches into window moving mode in Gnome. Other buttons aren’t affected.
-
@ruarí: The shows when you enable the show version in status bar does not fully work until after a browser restart (you get the Vivaldi snapshot icon but no text until after a restart).
Seen with dark mode
-
Known Issues
[Pop-out video][macOS][Linux] Mute button on PiP window is unclickable (VB-69378) -
@rluik I have overlooked this. Seems like mute button only works on Windows.
-
@pathduck: Hi. Yes, I can reproduce and it is a bug in the code that examines if elements should be removed. It tests for the wrong origin value (you can see that value your before-upgrade-file).
-
@espen OK, thanks! Any way I can avoid it happening again on my end, like changing
"origin": 2
to something else?