Unexpected behavior of "Window Behavior" -> "Window Actions"

I’m on KDE Plasma (Wayland session) 6.3.4 on Debian testing/Trixie.

What I’d like to do is set up Plasma such that clicking on the contents of an inactive window only raises and activates the window, instead of raising, activating, and passing the click.

This is under System SettingsWindow ManagementWindow BehaviorWindow ActionsInactive Inner Window ActionsLeft Click:.

What I want to have happen is Activate and raise, only. This is the behavior that I’m used to from my Mac OS X days.

The setting works for Middle click: and Right click:.

But for Left click:, you get a different outcome than you’re requesting:

With System Settings and a Dolphin window open, setting Left click: to Activate, pass click, and raise on release does exactly what you’d expect it to.

Setting it to Activate, raise and pass click activates the window and passes the click, but does not raise it.

Setting it to Activate and pass click activates the window, but does not raise it or pass the click.

Setting it to just Activate activates and raises the window, but does not pass the click.

Setting it to Activate and raise passes the click without raising the window or activating it.

Sounds like a config file is a little turned around somewhere in the build process?? :wink:

So, just to have a convenient “crib note:”

APCRR = Activate, pass click, and raise on release
ARPC = Activate, raise and pass click
APC = Activate and pass click
A = Activate
AR = Activate and raise

Mode  A? R? P? D?
APCRR y  y  y  y
ARPC  y  n  y  n
APC   y  n  n  n
A     y  y  n  n
AR    n  n  y  n

Legend:
A? Activates?
R? Raises?
P? Passes click?
D? On release? (Delayed?)

Just FYI, I did read this topic, which has similar issues, but didn’t have a resolution.

My system info

Hi!

This particular case has been reported through the KDE Bugtracking System here: 501457 – Inactive Inner Window Action "Activate, raise and pass click" does not raise the window

I’d recommend adding your observations, as detailed out here, into a comment on that bug report - that way, the connected issues with that particular configuration option can be investigated and handled together :slight_smile: