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. ***
Although this issue is referenced from:
that page currently says to go to "about:preferences" in Firefox to change mousewheel.with_alt.action to 1. It should say "about:config" instead of "about:preferences". I realize this may not be the ideal place to report this documentation error, but I don't have permission to edit that page and it wasn't clear where such errors should be reported. Perhaps someone monitoring this bug has the necessary permission.
Oops, that's my mistake! Thanks for the note. I'll correct it.
I cannot reproduce this on my Rawhide anymore. This was very likely resolved by:
i.e. by gtk3 3.24.19. Therefore F32+ should be probably OK.
Might be worth a backport to F31...the bug is against 31, so let's leave it open for now at least.
I can confirm it works ok now in F32.
The original report was actually against F30 and was moved to 31 later.
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 31 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
I cannot reproduce the issue either. Let's close this bug.