Originally created by @xidsyed on GitHub (Sep 2, 2024).
Describe the bug
A minimsed window, when attempted to be brought to the foreground with alt-tab doesnt focus until you click on it, even though komorebi draws a border around it.
UPDATE : On further investigation, this only happens when focusing an application on a blank workspaace, or in other words, when on a blank workspace (that may contain other minimised windows) a window of that workspace is brought to focus using alt tab.
To Reproduce
Steps to reproduce the behavior:
Minimse a window
press alt tab to bring it into focus
Expected behavior
Window should be in focus, and should respond to komorebi hotkeys and commands.
OS Name: Microsoft Windows 11 Home
OS Version: 10.0.22631 N/A Build 22631
komorebi 0.1.28
tag:v0.1.28
commit_hash:0cdce8fc
build_time:2024-07-15 16:06:31 +00:00
build_env:rustc 1.79.0 (129f3b996 2024-06-10),stable-x86_64-pc-windows-msvc
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 2, 2024).
**Describe the bug**
A minimsed window, when attempted to be brought to the foreground with alt-tab doesnt focus until you click on it, even though komorebi draws a border around it.
**UPDATE** : On further investigation, this only happens when focusing an application on a **blank workspaace**, or in other words, when on a **blank workspace** (that may contain other minimised windows) a window of that workspace is brought to focus using alt tab.
**To Reproduce**
Steps to reproduce the behavior:
1. Minimse a window
2. press alt tab to bring it into focus
**Expected behavior**
Window should be in focus, and should respond to komorebi hotkeys and commands.
**Screenshots and Videos**
https://github.com/user-attachments/assets/4b99e35d-cec5-4e2f-9cb9-1ba076e2f398
**Operating System**
```
OS Name: Microsoft Windows 11 Home
OS Version: 10.0.22631 N/A Build 22631
komorebi 0.1.28
tag:v0.1.28
commit_hash:0cdce8fc
build_time:2024-07-15 16:06:31 +00:00
build_env:rustc 1.79.0 (129f3b996 2024-06-10),stable-x86_64-pc-windows-msvc
```
**`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:53 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @xidsyed on GitHub (Sep 2, 2024).
Describe the bug
A minimsed window, when attempted to be brought to the foreground with alt-tab doesnt focus until you click on it, even though komorebi draws a border around it.
UPDATE : On further investigation, this only happens when focusing an application on a blank workspaace, or in other words, when on a blank workspace (that may contain other minimised windows) a window of that workspace is brought to focus using alt tab.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Window should be in focus, and should respond to komorebi hotkeys and commands.
Screenshots and Videos
https://github.com/user-attachments/assets/4b99e35d-cec5-4e2f-9cb9-1ba076e2f398
Operating System
komorebic checkOutput@LGUG2Z commented on GitHub (Jan 23, 2025):
I cannot reproduce this so I'm assuming it was fixed along the way 🎉