resurfaced multi-monitor focus shenanigans from #15075

[fxzzi]

pr #15075 has resurfaced the previously fixed issue #4649
movetoworkspace to an empty workspace on a different monitor, with follow_focus 2, the window on the other monitor is still focused

and clicking on an empty monitor doesn't move focus again

[vaxerski]

dam

[fxzzi]

Muh regressions

[vaxerski]

can you give me a repro case because it all works correctly on my end

[fxzzi]

hyprctl eval 'hl.config({ input = { follow_mouse = 2;}})'
hyprctl dispatch "hl.dsp.focus({monitor = 'DP-2'})"
sleep 1
hyprctl dispatch "hl.dsp.exec_cmd('foot')"
sleep 1
hyprctl dispatch "hl.dsp.focus({monitor = 'DP-3'})"
sleep 1
hyprctl activewindow

where DP-3 is empty. hyprctl activewindow should return invalid, as there should be no activewindow on that monitor, however it still returns the foot window from the other monitor.

[LAST7]

I think I might run into this as well. I was about to post a new discussion, but I found yours here. Not exactly the same(I use follow_mouse = 1), but quite similar it seems.

---

This is what I was about to post:

Description of the Issue / Behavior

On a multi-monitor setup with input:follow_mouse = 1, cursor:no_warps = true and warp_on_change_workspace = 0, switching a monitor to an empty workspace via keyboard shortcuts causes focus to immediately leak to the other monitor where the cursor is at.

workspace rule config:

for i = 1, 5 do
    hl.workspace_rule({ workspace = tostring(i), monitor = "DP-1", persistent = true })
    hl.workspace_rule({ workspace = tostring(i + 5), monitor = "DP-2", persistent = true })
end

Steps to Reproduce

1. Set follow_mouse = 1 and cursor:no_warps = true.(Also warp_on_change_workspace = 0)
2. Have windows open on Monitor 1 and Monitor 2. Focus is currently on Monitor 1, cursor is currently on Monitor 2.(Switch focus to window on Monitor 1 where cursor is not hovering on with keyboard hl.dsp.focus({ direction = "l/r" }))
3. Use a keyboard shortcut to change Monitor 1 to an empty workspace. ( hl.dsp.focus({ workspace = "m+1/m-1" }) )
4. Because the cursor stays stationary (due to no_warps = true), it is now physically hovering over a window on Monitor 2.
5. Hyprland immediately shifts keyboard focus to the window on Monitor 2. Waybar simultaneously shows both workspaces as "active/focused".

The Problem

If no_warps = false is used, the cursor jumps to the empty monitor and focus is preserved. However, for users who prefer their cursor to stay stationary (no_warps = true), there seems to be no way to stop an empty workspace from giving up focus to whatever window happens to sit under the cursor on the adjacent monitor, causing a continuous & one-directional workspace switching to 'cross' to another monitor. mouse_refocus = false does not alter this behavior.

It would be incredibly helpful to have an explicit setting (e.g., misc:allow_empty_workspace_focus or an extension to no_warps) that forces Hyprland to respect the monitor targeted by the keyboard workspace dispatcher, treating the (opened) empty monitor/workspace as an explicit focus block until the mouse is actively moved by the user.

---

Thank you for the post and thanks to the developers for looking into this and for any reply or fix.

[vaxerski]

#15374