54.0.2952.41 - Mouse back/forward buttons work as clicked twice.
-
adwil last edited by
First of all - I reported this error using Opera Bug Report Wizard on May 28th while it was happening in Opera Beta. Bug report got ID: DNAWIZ-29482. I didn't get any reply.
You can reproduce this error only if your mouse has extra backward/forward buttons.
Clicking mouse back button goes back by 2 pages instead of 1, example:
I'm on site A then I navigate to site B and then to C. Pressing backward mouse button gets you to site A instead of site BWhen i click and hold back button on my mouse then opera goes back by only one site, then I release that button and it goes back one more page. Same thing happens with forward button. I checked that on 2 different computers running Linux Mint with 2 different mouses. Button numbers in xinput test are the same for both computers so I assume that it's error that could possibly affect more users than just me. Strangely enough this behavior does not occur on Windows.
I checked which buttons are clicked exactly on my mouse by terminal command "xinput test <device_id>", it seems that someone changed opera's behavior by triggering forward/backward navigation on both key press and release:
button press 8
button release 8
button press 9
button release 9 -
-
A Former User last edited by
Same here, extremely annoying, may have to switch to chrome for a while. This is happening on Ubuntu 18.04LTS. Also, happening only in Opera. Registers press as click, and release as clicks, on forward and back buttons.
-
A Former User last edited by
Same here, openbox on debian testing x64. I thought my mouse was broken.
-
-
tc12 last edited by
Same issue in Ubuntu 18.04. This looks just like a Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=821253
-
-
A Former User last edited by
@tc12 said in 54.0.2952.41 - Mouse back/forward buttons work as clicked twice.:
Same issue in Ubuntu 18.04. This looks just like a Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=821253
I do not have it on chromium 67, and I do not recall having it on 66 either...
-
-
-
patrik-modesto last edited by
Hi, I was hit by this bug too and now it seems like it's fixed in version 55.0.2994.14 .
