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]: WhatsApp application doesn't conform to workspaces #314

New Issue
Closed
opened 2026-01-05 14:49:39 +01:00 by adam · 1 comment
adam commented 2026-01-05 14:49:39 +01:00
Owner
Copy Link

Originally created by @GAlcaraz on GitHub (Mar 17, 2024).

Describe the bug
Using the WhatsApp windows application is not possible with Komorebi. It seems it just stays on top of every workspace while switching, and isn't actually snapped to any workspace/zone.

To Reproduce
Steps to reproduce the behavior:

  1. Open 1 or more apps on different workspaces
  2. Open WhatsApp application
  3. Switch between different workspaces
  4. WhatsApp app window stays on top of other windows, never gets snapped nor leaves focus when switching.

Expected behavior
WhatsApp window should be treated as any other window

Screenshots and Videos
In case it's not clear what's happening, I'm pressing Alt+Workspace to switch between 2 different workspaces. I'm also clicking directly on one of the browser windows in order to leave the WhatsApp app behind it, and when I switch workspaces again WhatsApp gets back on top.
https://www.loom.com/share/6679726288f74dbdbbe4efd0159afe82?sid=cf3a9f1f-ab6e-453d-9e7f-699b49a935d3

Operating System

OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22621 N/A Build 22621

komorebic check Output

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\{USER}

Looking for configuration files in C:\Users\{USER}

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

Found C:\Users\{USER}\.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 @GAlcaraz on GitHub (Mar 17, 2024). **Describe the bug** Using the WhatsApp windows application is not possible with Komorebi. It seems it just stays on top of every workspace while switching, and isn't actually snapped to any workspace/zone. **To Reproduce** Steps to reproduce the behavior: 1. Open 1 or more apps on different workspaces 2. Open WhatsApp application 3. Switch between different workspaces 4. WhatsApp app window stays on top of other windows, never gets snapped nor leaves focus when switching. **Expected behavior** WhatsApp window should be treated as any other window **Screenshots and Videos** In case it's not clear what's happening, I'm pressing Alt+Workspace to switch between 2 different workspaces. I'm also clicking directly on one of the browser windows in order to leave the WhatsApp app behind it, and when I switch workspaces again WhatsApp gets back on top. https://www.loom.com/share/6679726288f74dbdbbe4efd0159afe82?sid=cf3a9f1f-ab6e-453d-9e7f-699b49a935d3 **Operating System** ``` OS Name: Microsoft Windows 11 Pro OS Version: 10.0.22621 N/A Build 22621 ``` **`komorebic check` Output** ``` No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\{USER} Looking for configuration files in C:\Users\{USER} Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\{USER}\.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:39 +01:00
adam closed this issue 2026-01-05 14:49:39 +01:00
adam commented 2026-01-05 14:49:39 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Mar 17, 2024):

WhatsApp is unfortunately a very problematic application that throws most of the established conventions of Windows GUI app development to the wind, because the window it launches (WhatsApp.exe with a class of Windows.UI.Core.CoreWindow) is not the window that you see and interact with.

  "manage_rules": [
    {
      "kind": "Exe",
      "id": "ApplicationFrameHost.exe",
      "matching_strategy": "Equals"
    }
  ],

You can add this very broad manage rule to your personal config to force-manage the actual WhatsApp window that you interact with, but there are also other applications that it may be undesirable to tile which will share this same exe. You'll probably need to minimize and restore the WhatsApp window after applying this rule, and after starting komorebi for the first time for it to take effect (because the app window initially gets misreported as I mentioned above).

At some point we'll need to look into composite manage rules (ie. matching on this exe && a custom title), but this is not currently possible.

@LGUG2Z commented on GitHub (Mar 17, 2024): WhatsApp is unfortunately a very problematic application that throws most of the established conventions of Windows GUI app development to the wind, because the window it launches (`WhatsApp.exe` with a class of `Windows.UI.Core.CoreWindow`) is not the window that you see and interact with. ```json "manage_rules": [ { "kind": "Exe", "id": "ApplicationFrameHost.exe", "matching_strategy": "Equals" } ], ``` You can add this very broad manage rule to your personal config to force-manage the actual WhatsApp window that you interact with, but there are also other applications that it may be undesirable to tile which will share this same exe. You'll probably need to minimize and restore the WhatsApp window after applying this rule, and after starting komorebi for the first time for it to take effect (because the app window initially gets misreported as I mentioned above). At some point we'll need to look into composite manage rules (ie. matching on this exe && a custom title), but this is not currently possible.
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#314
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?