I've noticed over the last few days, but haven't yet found a definitive pattern to reproduce it, that Vivaldi seems to 'miss' right clicks on the tabbar / toolbar areas. It always responds on a second click, but often the first is just swallowed. I just noticed it now when creating 4 new tabs and pasting URLs from a text editor into them. Once I had the 4 set up, I selected them with SHIFT+CLICK and then right-clicked to make a stack. But the right-click didn't produce the menu on the first attempt. Second attempt worked fine, and the stack was made. Not this clearly wasn't a focus issue, as I'd just selected the 4 tabs in question. I also noticed it when right-clicking on the 'Back' icon to get page history - it needed 2 clicks to get the list. Anyone else noticed this? I'm presuming it's windows-specific, and I'm on Windows 8.1 Pro 64-bit.
OK - just happened twice more, and I think I can reproduce it now. Boy is it weird. It's specifically related to switching tabs using the mouse scroll wheel. This is what I did:
Create 3 new blank tabs
Switch (click) to the first and enter a URL (e.g. google.com)
Switch (scoll) to the second and repeat (same or different URL)
Switch (scroll) to the third and repeat
Shift-click on the first to select the 3 tabs
Right-click to get the menu to, er, wait, where's the menu?
Right-click again to get the menu to create a stack
Note this works perfectly if you click to switch tabs.
Is what you're experiencing like this? – https://vivaldi.net/forum/vivaldi-browser-for-mac/9206-right-click-on-tabs-doesn-t-work-properly
Yes, very similar symptoms. I'm finding the organisation of the forum a little tricky though, as I use Vivaldi exclusively on Windows, and wasn't sure how to decide which category to post in. Looks like they had the same dilemma .
In any case, it's definitely 'triggered' by seomething, as once I've right-clicked twice on the tab area, the menu does come up as it should each time. Eventually though, it goes back to needing 2 clicks (I've never seen it need 3 as per that post).
I've now found an even simpler way to reproduce the bug (at least for me):
- Make sure you have at least 2 tabs open
- Right-click on the first (in the main window) to bring up the browser context menu
- Now switch tabs using the mouse scroll feature (clicking doesn't cause the problem)
- Right-click on the main window area again - it takes 2 clicks to get the context menu
My recipe above though does trigger the problem every time, so maybe that will help track it down… Can I add it to that bug that was filed? Should I file a new one? Still finding my way here...
I'm just another user here like you, so i don't know the answer to your last question. Maybe someone else with more knowledge than i have might soon chip in here to answer you?
PS - Wrt your "I'm finding the organisation of the forum a little tricky though, as I use Vivaldi exclusively on Windows, and wasn't sure how to decide which category to post in", if you set your view to "Forum - Recent Posts", you'll see recent posts across all topics. Obviously you won't bother reading any individual thread that looks uninteresting to you, but the benefit is that, given many themes seem to cross any one OS, it's easier for you to then keep abreast. FYI.
I'm finding the organisation of the forum a little tricky though, as I use Vivaldi exclusively on Windows, and wasn't sure how to decide which category to post in.
When checking for "similar problems" I try to check "Windows" and "All platforms" then quickly scan "Mac" and "Unix".
When finding one, add information (including system). Sometimes just a "me too, but on Windows 10" is enough.
If posting a "new" one, just post in the Windows forum. Users on other systems may spot it and can comment as above.
Can I add it to that bug that was filed? Should I file a new one? Still finding my way here…
The Vivaldi Bug system is closed to general public so we can't see it or add to it.
If you feel the info is useful, my suggestion would be to create a new Bug and refer to the other bug number in your report details.
The devs will then be able to sort it out.
Note: Still treat it a new report giving full details, just in case there is "something" different.
I imagine they spent quite a bit of time sorting duplicate reports as it is (because of the closed system).