Originally created by @F1orian on GitHub (Oct 11, 2022).
Describe the bug
The active window border is not equally thick on all sides for some applications (Firefox, Chrome, VSCode, ...)
To Reproduce
Steps to reproduce the behavior:
Enable Borders
2.Open One of the named applications
Un-focus and re-focus the window
Expected behavior
equal border with on all sides
Screenshots and Videos
Operating System
Provide the output of systeminfo | grep "^OS Name\|^OS Version"
For example:
OS Name: Microsoft Windows 10 Enterprise LTSC
OS Version: 10.0.19044 Nicht zutreffend Build 19044
Originally created by @F1orian on GitHub (Oct 11, 2022).
**Describe the bug**
The active window border is not equally thick on all sides for some applications (Firefox, Chrome, VSCode, ...)
**To Reproduce**
Steps to reproduce the behavior:
1. Enable Borders
2.Open One of the named applications
3. Un-focus and re-focus the window
**Expected behavior**
equal border with on all sides
**Screenshots and Videos**

**Operating System**
Provide the output of `systeminfo | grep "^OS Name\|^OS Version"`
For example:
```
OS Name: Microsoft Windows 10 Enterprise LTSC
OS Version: 10.0.19044 Nicht zutreffend Build 19044
```
adam
added the bug label 2026-01-05 14:48:34 +01:00
Is this what the komorebic identify-border-overflow-application command is for? Genuinely asking, because I'm not sure.
@maxbane commented on GitHub (Oct 17, 2022):
Is this what the `komorebic identify-border-overflow-application` command is for? Genuinely asking, because I'm not sure.
Is this what the komorebic identify-border-overflow-application command is for? Genuinely asking, because I'm not sure.
This command is primarily to identify Electron applications that deliberately overflow the system-wide fixed invisible borders around every window.
There currently is no command exposed to modify the width of the active window border, though from the screenshot I believe this may be something specific to Windows 10 (which I'm not running anymore) if the generated configuration file with application-specific fixes has been applied.
For anyone who wants to work on this, I'd suggest two ways forward: Exposing a command to manually configure active border widths, or adding a Windows 10-specific logic fork to the current border width calculation values.
@LGUG2Z commented on GitHub (Oct 17, 2022):
> Is this what the `komorebic identify-border-overflow-application` command is for? Genuinely asking, because I'm not sure.
This command is primarily to identify Electron applications that deliberately overflow the system-wide fixed invisible borders around every window.
There currently is no command exposed to modify the width of the active window border, though from the screenshot I believe this may be something specific to Windows 10 (which I'm not running anymore) if the generated configuration file with application-specific fixes has been applied.
For anyone who wants to work on this, I'd suggest two ways forward: Exposing a command to manually configure active border widths, or adding a Windows 10-specific logic fork to [the current border width calculation values](https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/border.rs#L108).
Setting custom border widths and offsets is now supported with komorebic commands: active-window-border-width and active-window-border-offset.
@LGUG2Z commented on GitHub (Jan 22, 2023):
Setting custom border widths and offsets is now supported with `komorebic` commands: `active-window-border-width` and `active-window-border-offset`.
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 @F1orian on GitHub (Oct 11, 2022).
Describe the bug
The active window border is not equally thick on all sides for some applications (Firefox, Chrome, VSCode, ...)
To Reproduce
Steps to reproduce the behavior:
2.Open One of the named applications
Expected behavior
equal border with on all sides
Screenshots and Videos

Operating System
Provide the output of
systeminfo | grep "^OS Name\|^OS Version"For example:
@maxbane commented on GitHub (Oct 17, 2022):
Is this what the
komorebic identify-border-overflow-applicationcommand is for? Genuinely asking, because I'm not sure.@LGUG2Z commented on GitHub (Oct 17, 2022):
This command is primarily to identify Electron applications that deliberately overflow the system-wide fixed invisible borders around every window.
There currently is no command exposed to modify the width of the active window border, though from the screenshot I believe this may be something specific to Windows 10 (which I'm not running anymore) if the generated configuration file with application-specific fixes has been applied.
For anyone who wants to work on this, I'd suggest two ways forward: Exposing a command to manually configure active border widths, or adding a Windows 10-specific logic fork to the current border width calculation values.
@LGUG2Z commented on GitHub (Jan 22, 2023):
Setting custom border widths and offsets is now supported with
komorebiccommands:active-window-border-widthandactive-window-border-offset.