starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: Floating Winodow Loses Focus upon Return To Workspace #464

New Issue
Closed
opened 2026-01-05 14:50:54 +01:00 by adam · 2 comments
adam commented 2026-01-05 14:50:54 +01:00
Owner
Copy Link

Originally created by @xidsyed on GitHub (Sep 4, 2024).

Describe the bug
A focused floating window in komorebi will lose focus, when switching to different workspace and returning. I have attached a video showcasing the behaviour

To Reproduce

  1. Float a window on a workspace
  2. Switch to a different workspace
  3. Switch back

Expected behavior
The floating window should have remained in focus, but it doesn't

Screenshots and Videos

https://github.com/user-attachments/assets/261c3b56-f3d2-40bb-b58a-265a6ed2c6fd

Operating System
Provide the output of systeminfo | grep "^OS Name\|^OS Version"

OS Name:                   Microsoft Windows 11 Home
OS Version:                10.0.22631 N/A Build 22631

komorebic check Output

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\mmsye

Looking for configuration files in C:\Users\mmsye

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

Found C:\Users\mmsye\.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 @xidsyed on GitHub (Sep 4, 2024). **Describe the bug** A focused floating window in komorebi will lose focus, when switching to different workspace and returning. I have attached a video showcasing the behaviour **To Reproduce** 1. Float a window on a workspace 2. Switch to a different workspace 3. Switch back **Expected behavior** The floating window should have remained in focus, but it doesn't **Screenshots and Videos** https://github.com/user-attachments/assets/261c3b56-f3d2-40bb-b58a-265a6ed2c6fd **Operating System** Provide the output of `systeminfo | grep "^OS Name\|^OS Version"` ``` OS Name: Microsoft Windows 11 Home OS Version: 10.0.22631 N/A Build 22631 ``` **`komorebic check` Output** ``` No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\mmsye Looking for configuration files in C:\Users\mmsye Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\mmsye\.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:50:54 +01:00
adam closed this issue 2026-01-05 14:50:54 +01:00
adam commented 2026-01-05 14:50:54 +01:00
Author
Owner
Copy Link

@gursuj commented on GitHub (Jan 3, 2025):

I am facing the opposite bug where switching to a workspace with a floating window will always focus the floating window, regardless of what the last focused window was. Not sure if that should be a separate issue?

@gursuj commented on GitHub (Jan 3, 2025): I am facing the opposite bug where switching to a workspace with a floating window will always focus the floating window, regardless of what the last focused window was. Not sure if that should be a separate issue?
adam commented 2026-01-05 14:50:54 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 23, 2025):

Floating windows are rendered at the top of the Z order when switching to a workspace where they are contained - this is going to be the intended behavior going forward

@LGUG2Z commented on GitHub (Jan 23, 2025): Floating windows are rendered at the top of the Z order when switching to a workspace where they are contained - this is going to be the intended behavior going forward
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#464
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?