"For all Apps" Trigger stopps working when Firefox specific Trigger is configured

Hello,

I've run into the following Unexpected behavior and would be happy to get assistance with solving this.

Describe the bug

  • I've setup the BTT Window Switcher to work with my mouse (see BTTWindowSwitcher.bttpreset (26.3 KB))

  • These triggers are setup under "For all Apps" and is working fine for all Apps

  • Once I create and activate the Firefox specific Trigger (see TabScrolling.bttpreset (11.7 KB)), there are different misbehavior (sometimes 1 occurs sometimes 2 occurs):

1. Window Switcher preset stops working when Firefox is the focused window

  • even if I disable the TabScrolling Triggers the WindowSwitcher still does not work when Firefox is the focused window
  • I need to delete the TabScrolling Triggers to get the WindowSwitcher back to work

2. The TabScrolling Triggers do not work in Firefox

  • They just don't trigger

I have not figured out under which circumstances 1 or 2 occurs.

Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):

  • Mouse (I've tested the Logitech MX Master 4 and MX518)

Screenshots
TabScrolling Triggers:

Window Switcher Triggers:


Device information:

  • Type of Mac: MacBook Pro M4
  • macOS version: 26.0.1
  • BetterTouchTool version: 5.731

Additional information (e.g. crash logs, related issues, etc.):

  • Please let me know if I can assist with anything.

Does anyone have an idea where this misbehavior could come from and what I could do to analyze it further?

I've tried to look at the "Recently Used" Triggers but the triggers are just not executed.

Could this be caused by the fact that both triggers listen on Mouse-Wheel "Scroll Up/Down" but with different "Advanced Conditions". Is this something that is not supported!?

It is most likely related to the advanced conditions because in case of mouse triggers BTT currently doesn't loop through all matching conditions across apps until it finds one that is true. I think it just checks the first one and if that is not true it will fallback to the default behavior.

This is mostly for performance reasons.

You could workaround it by moving your window switcher triggers to a conditional activation group that is always true except for when firefox is active.

1 Like

Wouldn't that cause that the Window Switcher no longer works in Firefox?

I want the Window Switcher to work on all Apps (including Firefox).

The TabScrolling should only work in Firefox.

So I guess I need to move the TabScrolling to a conditional activation group as you suggested.

Will give it a try later today or tomorrow morning and keep you posted.

Thank you Andreas and have a great evening.

I tried to solve the topic with the conditional activation group and tried the following:

  1. I set up a CAG as suggested by Andreas (NOT (appName CONTAINS "Firefox") and moved the Window Switcher in this CAG --> no success
  2. I set up a CAG (appName CONTAINS "Firefox") and moved the TabScrolling in this CAG --> no success

I had the behavior that WindowSwitcher worked fine and TabScrolling didn't work (Misbehavior 2)

Then I deactived all TabScrolling in the Firefox App and recreated those Triggers from scratch. Now I am back in misbehavior 1 were TabScrolling works in Firefox but Window Switcher do not work in Firefox.

Again, even after deactivating the newly created triggers the Window Switcher still does not work in Firefox (as in the original report). This feels very random.

I guess the conditional activation group cannot solve my problem!? Since I want different triggers working for Firefox when I scroll the wheel depending on, if I press the mouse_button_1, mouse_button_2 or mouse_button_6 while scrolling.

Any more ideas?

I found a workaround solution by setting up the TabScrolling Shortcuts for Firefox in Better-Mouse instead of Better Touch Tool.

Hi Andreas,
I was wondering if the new "Actions Executed on..." functionality could be enhanced to support the UseCase from this topic?

Since BTT now supports all Logitech functions I got rid of BetterMouse - so my Workaround is no longer working.

So introducing the MouseWheels into the "Actions Executed on..." section would help me a lot.

  • Action Executes on Scroll Up
  • Action Executes on Scroll Down
  • Action Executes on Scroll Left
  • Action Executes on Scroll Right

I don't know if this is technically feasible and reasonable - what do you think?

Best regards,
Volker

While I probably won't be able to solve this via Action Categories, the latest alphas support to record button combinations and even button+scroll wheel combinations like this:

I have not yet tried whether that would resolve your issue, but it might because no advanced conditions would be required anymore if I understood correctly.

1 Like

You are like a genie in a bottle - It feels like 4 out of 5 feature requests I put into this forum are already there.

Thank you so much - it works, but I somehow had to restart BTT after I set it up.

Have a great Saturday evening and enjoy your Sunday.