Border stays 1 second after minimizing the window

[mancha97]

At first, I don't recall the border being this laggy. It feels like the border stays ~1.5s after minimizing the window. Is there a way I can change this behavior? It feels like after some use it has become laggy. Ideally I would like to make the border disappear at the same time the window is minimized.

I like JankyBorders but is making my macbook look old and laggy. I'm using it with aerospace and I have this configured in my aerospace.toml file:

after-startup-command = [
# JankyBorders has a built-in detection of already running process,
# so it won't be run twice on AeroSpace restart
'exec-and-forget borders active_color=0xffe1e3e4 inactive_color=0xff494d64 width=5.0'
]

Not sure if this affects this behavior.

[FelixKratz]

I am pretty sure this is connected to the new window launch and close animations in tahoe, because if you run

defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool false

this does not happen anymore.

[mancha97]

@FelixKratz Thanks for replying. I'm running Sonoma (Tahoe doesn't have good reviews on a M1 Macbook Air). I ran this command but didn't help. I'll share with you a little gift so you can see the behavior:

(I know it looks a little chopped due the gif quality but indeed that's how it feels in real life as well)

[anarqist]

I am pretty sure this is connected to the new window launch and close animations in tahoe, because if you run

defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool false
this does not happen anymore.

Tried this command on macOS 26.0.1 with no success.
It also appears when a window is minimized and you open it again, the border appears first and then the app window is there.

I've only this in my bordersrc file:

#!/bin/bash

options=(
	style=round
	width=6.0
	hidpi=on
	active_color=0xffca9ee6
	inactive_color=0xfff4b8e4
)

borders "${options[@]}"

[kerryj89]

defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool false

Works for me for closing animation on Tahoe 26.0.1, though it adds a very slight delay to actually minimizing now (I'm guessing it still waits for the animation's timeline even though it's not playing it).

Unfortunately activating a minimized window draws the border immediately before the window unminimizes into place.

[IvanKoskov]

Can not fix it as well. I used the defaults to minimize the animations, but it does change the situation. Somebody has an advice?

[kerryj89]

Idk, but I find humor in the name JankyBorders further living up to the name (obviously not the devs fault).

[mancha97]

@FelixKratz I like this project. Is there any way to help you to fix this tiny bug? I see the project it's currently maintained by you only.

[FelixKratz]

The problem boils down to availability of system events. All I am really doing here is registering a series of system events for windows. There is an event for when a window is closed and we handle this event directly when it is emitted. This means if the system (for whatever reason) decides to only send the window close event after the close animation is fully completed, we need so look for a new event that is emitted once the close animation is started (or disable the animation). I am not aware of such event.

Then there is the problem that some (arguably ill-behaved) apps might not actually close a window (on a system level) when you click the close button, but rather clear its content and just make it transparent, and only after some time call the system level window close function, likely deferred. Of course we have no information about this happening in jb, where we simply rely on the system level events sent to us by the system.