Open Bug 1883178 Opened 3 months ago Updated 2 months ago

[regression] Double finger click is no longer correctly recognized

Categories

(Firefox :: Tabbed Browser, defect)

Firefox 123
defect

Tracking

()

UNCONFIRMED

People

(Reporter: bluedzins, Unassigned, NeedInfo)

Details

Steps to reproduce:

On systems with single mouse button like MacBook, you trigger RMB by (for example) pressing touchpad with two fingers at the same time.

I pressed touchpad with two fingers.

Actual results:

LMB click was registered.

Expected results:

RMB click should be registered.

And it worked like this previously, 102.6.0esr was fine in this regard. I am not saying regression occurred in version 123, but for sure the regression is already there.

I am unable to replicate your issue in the most recent versions of Nightly 125.0a1 and Firefox 123.0.1 on macOS 11.
In order to further diagnose and isolate the problem, could you please conduct a test in Safe Mode to determine if the issue persists under those conditions? Additionally could you use a new profile and let me know if it's reproducible there too?

Flags: needinfo?(bluedzins)

I am very sorry for not being precise.

@Ina, could you please follow this steps:

  1. open two tabs within one Firefox
  2. using two fingers click somewhere within the page
  3. using two fingers click on the tab itself

While (2) works for me as before, (3) does not work currently (but worked in older version). And this is the same regardless if I use Safe/Troubleshooting mode or not.

Since you use macOS could you please check the behaviour on tabs? I mean tab bar, not content.

I've made repeated attempts to replicate the reported issue on macOS 11, following the additional STR mentioned in Comment 2, unfortunately without success.
Setting the component and currently awaiting the developer's input on this matter.
If this is not the correct component, please feel free to change it to a more fitting one.

Component: Untriaged → Tabbed Browser

One more clarification, I realized it now -- despite hardware mouse-wise is the same, we (Ina and me) are running different binaries. In my case it is Linux Firefox (I run openSUSE 15.3, and the 102.6.0esr was tailored specifically for it, while the new version of Firefox is downloaded from the FF webpage and it is generic Linux binary).

Flags: needinfo?(bluedzins)

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dao+bmo)

(In reply to macias from comment #0)

And it worked like this previously, 102.6.0esr was fine in this regard. I am not saying regression occurred in version 123, but for sure the regression is already there.

Would you mind running mozregression to help narrow down when this may have regressed?

Flags: needinfo?(dao+bmo) → needinfo?(bluedzins)

Sure, this is my findings. RMB = simulated by double finger click

  • I executed 102.6.0esr (installed via openSUSE repo) version to make sure, everything works as I described -- RMB works correctly both for page content and tab pane (bar)

  • I executed 124.0.1 -- RMB works only within page content

I found out that 102.6 initial release was 2022-12-13 (https://www.mozilla.org/en-US/firefox/102.6.0/releasenotes/?utm_source=firefox-browser&utm_medium=firefox-desktop&utm_campaign=about-dialog) so I executed:

~/.local/bin/mozregression --good 2022-12-13
**********
You should use a config file. Please use the --write-config command line flag to help you create one.
**********

 0:00.78 WARNING: You are using mozregression version 4.0.19, however version 6.0.2 is available.
 0:00.78 WARNING: You should consider upgrading via the 'pip install --upgrade mozregression' command.
 0:00.78 INFO: No 'bad' option specified, using 2024-03-28
 0:02.87 WARNING: Skipping build 2023-08-06: Unable to find build info for 2023-08-06

After a while "mozilla-central build for 2022-12-13" was executed. I repeated the test here and RMB is working only withing page content. So the behaviour is broken here is well.

Did I do something wrong with this test?

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