[BUG]: Dragging floating windows also moves tiled window underneath #327

New Issue

2026-01-05T14:49:45+01:00

adam commented

2026-01-05 14:49:45 +01:00

Originally created by @jpmiller25 on GitHub (Apr 5, 2024).

When I move a floating window from one monitor to another, the tiled window underneath also follows.

To Reproduce
Steps to reproduce the behavior:
2-monitor setup
Open tiled window on monitor A, e.g. browser.
Open floating window on monitor A, e.g. calculator.
Drag calculator from A to B and drop.
Browser gets moved from A to B.

Expected behavior
Tiled windows stay where they are, tiled windows can be moved freely on top.

Operating System

OS Name:                   Microsoft Windows 10 Business
OS Version:                10.0.19045 N/A Build 19045

komorebic check Output

KOMOREBI_CONFIG_HOME detected: C:\Users\jmiller\.config\komorebi

Looking for configuration files in C:\Users\jmiller\.config\komorebi

Found komorebi.json; this file can be passed to the start command with the --config flag

Found C:\Users\jmiller\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag

Originally created by @jpmiller25 on GitHub (Apr 5, 2024). When I move a floating window from one monitor to another, the tiled window underneath also follows. **To Reproduce** Steps to reproduce the behavior: 2-monitor setup Open tiled window on monitor A, e.g. browser. Open floating window on monitor A, e.g. calculator. Drag calculator from A to B and drop. Browser gets moved from A to B. **Expected behavior** Tiled windows stay where they are, tiled windows can be moved freely on top. **Operating System** ``` OS Name: Microsoft Windows 10 Business OS Version: 10.0.19045 N/A Build 19045 ``` **`komorebic check` Output** ``` KOMOREBI_CONFIG_HOME detected: C:\Users\jmiller\.config\komorebi Looking for configuration files in C:\Users\jmiller\.config\komorebi Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\jmiller\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag ```

adam added the bug label 2026-01-05 14:49:45 +01:00

adam closed this issue

2026-01-05 14:49:45 +01:00

adam commented

2026-01-05 14:49:45 +01:00

@LGUG2Z commented on GitHub (Apr 5, 2024):

This also annoys the hell out of me when I run into it 😅

I'll try to look at this for v0.1.24.

@LGUG2Z commented on GitHub (Apr 5, 2024): This also annoys the hell out of me when I run into it 😅 I'll try to look at this for v0.1.24.

adam commented

2026-01-05 14:49:45 +01:00

@azinsharaf commented on GitHub (Apr 5, 2024):

i have seen this even on one monitor. if MS Teams is float and i move it with the mouse it retiles the windows behind it.

@azinsharaf commented on GitHub (Apr 5, 2024): i have seen this even on one monitor. if MS Teams is float and i move it with the mouse it retiles the windows behind it.

adam commented

2026-01-05 14:49:46 +01:00

@LGUG2Z commented on GitHub (Apr 5, 2024):

We probably need to update this check to also ensure that we only trigger this code path when the window that triggers the event is known to the workspace: https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/process_event.rs#L342

@LGUG2Z commented on GitHub (Apr 5, 2024): We probably need to update this check to also ensure that we only trigger this code path when the window that triggers the event is known to the workspace: https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/process_event.rs#L342

adam commented

2026-01-05 14:49:46 +01:00