Closed Bug 1805618 Opened 1 year ago Closed 1 year ago

Mouse wheel scrolling does not work when X-Mouse control is active

Categories

(Firefox :: Untriaged, defect)

Firefox 109
defect

Tracking

()

RESOLVED DUPLICATE of bug 1798014

People

(Reporter: martin, Unassigned)

Details

Steps to reproduce:

Windows 11 22h2
I have using X-Mouse button control to remap additional mouse buttons (copy/paste).
2.19.2, https://www.highrez.co.uk.
Actually button remaps works. Only page scrolling stops working.
Only button remapping is activated (intercepted) in X-mouse button control.

Actual results:

After 109(beta) update mouse wheel scrolling stops working when X-Mouse control is active.
After rollback to 108 - everything is ok.

I am having the same issue on Windows 10 22H2 19045.2364 using Firefox 109.0 beta 2 with X-Mouse Button Control running in background:

  • After today’s Firefox update from version 108.0 (20221208122842) to 109.0b2 (20221213185929) vertical scrolling within the browser with mouse wheel has stopped working.
  • Scrolling by pressing the wheel and moving the cursor upwards or downwards still works. So does scrolling with keyboard buttons.
  • Zoom with Ctrl+wheel also works.
  • Scrolling starts to work when Firefox is restarted in Troubleshoot Mode, but not when all Add-ons are disabled manually in normal mode.
  • It also works normally when XMouseButtonControl.exe process is stopped using Task Manager.

I was unable to find any set of settings for X-Mouse Button Control which would allow the scroll in Firefox to work. Scroll in apps other than Firefox seems to be unaffected by XMBC.

I managed to track down the XMBC option that causes the scroll problem to occur: “Make scroll wheel scroll window under cursor”. The workaround is to clear this general setting or enable a per-app setting “Disable Scroll Window Under Cursor” for firefox.exe.
Related: bug #1798014.

It seems to be a bug or at least an incompatibility affecting both Firefox and XMBC, and an optimal solution is to implement a fix in both applications. Patching only one of them should also solve the problem for the end users. This is probably happening at the moment, as there is a recent discussion about the bug also on XMBC’s forum.

For example, XMBC 2.20 Beta 7 seems to work without triggering the issue. It can be installed from within the app by enabling beta updates in settings and manually triggering a search for updates.

As there is a fix implemented in the Nightly version of Firefox as well, the bug can be probably closed as fixed or a duplicate of #1798014.

Based in comment 2 I will close this as duplicate of 1798014 which is already fixed.
Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1798014
Resolution: --- → DUPLICATE

(In reply to Piotr [:pdsz] from comment #2)

I managed to track down the XMBC option that causes the scroll problem to occur: “Make scroll wheel scroll window under cursor”. The workaround is to clear this general setting or enable a per-app setting “Disable Scroll Window Under Cursor” for firefox.exe.
Related: bug #1798014.

It seems to be a bug or at least an incompatibility affecting both Firefox and XMBC, and an optimal solution is to implement a fix in both applications. Patching only one of them should also solve the problem for the end users. This is probably happening at the moment, as there is a recent discussion about the bug also on XMBC’s forum.

For example, XMBC 2.20 Beta 7 seems to work without triggering the issue. It can be installed from within the app by enabling beta updates in settings and manually triggering a search for updates.

As there is a fix implemented in the Nightly version of Firefox as well, the bug can be probably closed as fixed or a duplicate of #1798014.

Sorry, I would just like to note that my patch doesn't actually fix this issue on Firefox; All it does is note that the issue was detected in about:support so that our engineers can easily track it down. As installing global mouse hooks is probably out-of-the-realm of things that Firefox should be doing, the only reasonable fix for this is for software like XMBC to handle disabled windows properly (which it now does in its newest Beta).

You need to log in before you can comment on or make changes to this bug.