Keyboard codes for Back and Forward trigger twice
-
@Gwen-Dragon You said could not be reproduced with Vivaldi 2.7, can I assume you mean 3.7? Also another slight mix up in your recent post, the keyboard problem was reported as VB-48118. (You quoted VB-48982, which I had mentioned but I was actually about something else in that paragraph, and that problem was fixed a long time ago, I can do my book shopping from Vivaldi now.)
I still see the keyboard problem here on Windows with the latest snapshot on Windows 10: Vivaldi.3.7.2218.3.x64
As noted earlier, the keyboard codes that are going wrong are VK_BROWSER_BACK and VK_BROWSER_FORWARD - different devices may be sending different codes. In fact I work around around the problem by using AutoHotKey to translate those codes into Alt+Left and Alt+Right, for Vivaldi, which it does handle correctly.
modeit Split from https://forum.vivaldi.net/topic/31768/using-mouse-buttons-to-go-back-takes-me-two-pages-back/
-
@Gwen-Dragon Thanks for your response. I have a work around that works for me. There is little point in re-raising the issue when your developers cannot see it happen there. I don't know why that should be (it seems consistent across hardware here), but I've been about as explicit as I can be, right down to the actual key codes that cause the problem here.
-
I described the problem in VB-48118. It is quite explicit. I don't really have anything to add to that - and I didn't even know you'd closed that report until your reply above, so I didn't even know you'd stopped looking.
As a software developer myself, I do understand that if you are unable to reproduce the problem it will be very difficult to resolve it. I have no explanation for why those key codes cause different responses here to what they do on your development machines.
If you want to try something with AutoHotKey, the following script will turn Ctrl+L into vk_browser_back, and Ctrl+R into vk_browser_forward. Running that here shows Vivaldi doing the two steps instead of one as described.
#IfWinActive ahk_exe vivaldi.exe ^l:: SendInput {Browser_Back} return ^r:: SendInput {Browser_Forward} return
If you replace that with the following, then Ctrl+L will issue Alt+Left and Ctrl+R will issue Alt+Right, and these then do what we want, going only one step back or forward.
#IfWinActive ahk_exe vivaldi.exe ^l:: SendInput !{Left} return ^r:: SendInput !{Right} return
-
Sorry, that "you" was the "royal you" - like the "royal we". I was referring to Vivaldi. No personal blame was intended. My apologies for the ambiguity.
I'm pleased you (personal or corporate
) can reproduce the problem using AutoHotKey.
It seems very likely that this is what other users have been reporting in that other thread. Years ago I had a Logitech mouse with wheel tilt left/right and it's default configuration was to issue these two keyboard codes. The main reason why I am familiar with AutoHotKey was using it to achieve the same result with mouses that won't let me configure this behaviour more directly ... because old habits die hard and I really like the wheel-tilt as back/forward.
Thank you for your efforts.
-
I am having the same problem with Strokesplus using
acSendKeys("{BROWSERBACK}")
acSendKeys("{BROWSERFORWARD}")Back and forward sends the operation twice
-
It still happens when I turn off keyboard shortcuts
-
So it appears the problem has changed. No longer are those keycodes being processed twice - now they are not being processed at all.
I am not sure exactly which release it changed, I have not had time lately to test against every release. I know the changed behaviour is happening now with snapshot v4.1.2339.3, and I first noticed it with v4.0.2312.11. At a guess it came in with v4.
Still no big deal to me personally, I use AutoHotKey to work around the problem, but I imagine it may be turning away people that find out Vivaldi isn't working as expected with their particular keyboard or mouse.
-
Happens on the UHK (Ultimate Hacking Keyboard) too. Seems to be a general VK_BROWSER_BACK and VK_BROWSER_FORWARD problem. Navigating twice here still on v4.1.2369.10.
-
This post is deleted! -
Let's see if 2022 finally brings a bugfix. Bug still exists in Vivaldi 5.0.
All my input devices (touchpad, mouse and media remote) send the VK_ codes so I need them to work flawlessly.
-
Ppafflick moved this topic from Vivaldi for Windows on