Description of problem:
When FF does not have focus, but the mouse cursor is above its window and I scroll the wheel, instead of scrolling the page, the history backward/forward is browsed.
Version-Release number of selected component (if applicable):
$ rpm -q firefox
Steps to Reproduce:
1. Browse FF.
2. Give focus to another then FF window
3. Move cursor above FF and scroll the wheel.
The history forward/backward is browsed
The page (or nothing) is scrolled.
I've been suffering from this too. It's insanely, incredibly annoying and drives me nuts. I have a two-display setup and Firefox is usually maximized on one display, so I run into this *all the time* when I want to scroll the page open in Firefox but a window on the other screen happens to have the focus.
Note this doesn't *always* happen, sometimes scrolling the wheel over the inactive Firefox window does scroll the page not browse the history. I think the difference is whether you change focus by clicking the other window (bug does not happen) or hitting alt-tab (bug does happen).
ALT + mouse wheel scrolls history on focused window. Looks like the ALT modifier remains active for Firefox when ALT+TAB is used and then the history scroll is used. I'll look at it.
That makes sense... and actually there's another thing I've been seeing lately which might *possibly* be related: the Firefox test in openqa has been failing quite often lately and always when trying to type something that involves a modifier key (e.g. ctrl-t to open a new tab, or just typing a colon). It might turn out not to be the same thing at all, of course, but I thought I'd mention it.
Can you confirm that this is Wayland only? I can't reproduce on X.
This is a Mutter bug, can be preproduced on simple testcase. Filed as https://gitlab.gnome.org/GNOME/mutter/issues/474
Thanks a lot!
*** Bug 1724092 has been marked as a duplicate of this bug. ***
*** Bug 1754265 has been marked as a duplicate of this bug. ***
It still entertains us on Fedora 31.
Moving to Gtk3 according to upstream ticket.
*** Bug 1758130 has been marked as a duplicate of this bug. ***