BUG: Middle clicking on a webpage can trigger unintentional actions...
-
My screenshots are showing tests done on a 1080p size screen.
There is a new bug in version 3.2, in which the mouse cursor position is bugged after we middle click on a webpage. When we middle click on a webpage, the mouse cursor invisibly moves down a certain distance, which can cause accidental hovering or clicking of items. The distance it moves down can vary depending on if we have the bookmarks bar hidden or showing, so the distance seems related to the size of the top UI. A very annoying bug. Please fix soon.
[bug reported VB-73767]
-
@TsunamiZ I am having trouble reproducing this bug. Are you using Windows scaling?
When I middle-click on that page, I get the fast scroll four-way arrow cursor and can scroll quickly up and down the page. No pop-ups appear in that mode.
Clicking anywhere with left, right, or middle buttons exits fast scroll mode and then the cursor position is correctly registered as far as I can tell. Enabling/disabling the Bookmark Bar (or the Panel or Status Bar) makes no difference.
-
i am not using any scaling.
the hovering effect you see in my screenshots is related to the mouse cursor invisibly moving down and hovering on a link during the middle click's page scroll mode, despite me originally middle clicking far above that link. after exiting the page scroll mode, the mouse returns to the original position. but the problem is that the mouse cursor invisibly moves a certain distance down while the page scroll move is active. the distance it moves seems related to the size of the top UI.
-
@TsunamiZ OK. I see it now. It can happen when you stop scrolling.
-
how many websites does this occur on..or is it just wikipedia.
-
it can happen on any website.
-
@TsunamiZ If it's that annoying auto-scroll feature that's involved in the problem, as seems to be implied above, there are ways to nix it:
https://forum.vivaldi.net/topic/32367/option-to-disable-middle-mouse-button-autoscrolling
-
can someone test if this bug still happens in version 3.2.1967.47?
-
does this bug still happen in version 3.3?
-
This post is deleted!
