I am having similar issue, and it's beyond annoying. Every time I try to use the scroll bar, it resizes and moves the window. Then when I hit the maximize button, instead of going back to full size, it moves the resized window to another location. So I have to hit the maximize button twice to get full size back. Just to repeat the process again when I attempt to scroll again. This started today when Opera updated to 103.0.4928.34. Never had this issue before.
Best posts made by turbotom64
-
RE: [Compilation]Discussions on Scrolling doesn't work if the mouse is on the edge of the screenGeneral
-
RE: [Compilation]Discussions on Scrolling doesn't work if the mouse is on the edge of the screenGeneral
Yet another upgrade to 104.0.4944.36 and still not fixed. This seems to a major issue to me that needs fixed ASAP. Even knowing about it, I still move the window when trying to scroll most of the time. I guess it's time for a new browser, cause this just sucks.
Latest posts made by turbotom64
-
RE: [Compilation]Discussions on Scrolling doesn't work if the mouse is on the edge of the screenGeneral
Updated to 105.0.4970.16, problem seems to be fixed!
-
RE: [Compilation]Discussions on Scrolling doesn't work if the mouse is on the edge of the screenGeneral
Yet another upgrade to 104.0.4944.36 and still not fixed. This seems to a major issue to me that needs fixed ASAP. Even knowing about it, I still move the window when trying to scroll most of the time. I guess it's time for a new browser, cause this just sucks.
-
RE: [Compilation]Discussions on Scrolling doesn't work if the mouse is on the edge of the screenGeneral
I am having similar issue, and it's beyond annoying. Every time I try to use the scroll bar, it resizes and moves the window. Then when I hit the maximize button, instead of going back to full size, it moves the resized window to another location. So I have to hit the maximize button twice to get full size back. Just to repeat the process again when I attempt to scroll again. This started today when Opera updated to 103.0.4928.34. Never had this issue before.