Skip to content

BUG: System input indicator should not be considered a window for event handling #2570

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kiangti opened this issue Mar 10, 2025 · 3 comments

Comments

@kiangti
Copy link

kiangti commented Mar 10, 2025

Image
The system input indicator triggered by input source changes in macOS is being recognized as a window, causing yabai to send window events like window_created and window_destroyed.

I believe the input indicator shouldn't trigger window-related events (e.g., window_created, window_destroyed) through yabai, regardless of whether it is shown or hidden.

I use this in yabairc to capture this window info:

yabai -m signal --add event=window_created action='yabai -m query --windows > ~/Desktop/windows.json'
{
	"id":161,
	"pid":1113,
	"app":"xxxxxx",
	"title":"",
	"scratchpad":"",
	"frame":{
		"x":733.0000,
		"y":586.0000,
		"w":84.0000,
		"h":77.0000
	},
	"role":"AXWindow",
	"subrole":"AXDialog",
	"root-window":true,
	"display":1,
	"space":1,
	"level":3,
	"sub-level":0,
	"layer":"above",
	"sub-layer":"normal",
	"opacity":1.0000,
	"split-type":"none",
	"split-child":"none",
	"stack-index":0,
	"can-move":true,
	"can-resize":false,
	"has-focus":false,
	"has-shadow":true,
	"has-parent-zoom":false,
	"has-fullscreen-zoom":false,
	"has-ax-reference":true,
	"is-native-fullscreen":false,
	"is-visible":true,
	"is-minimized":false,
	"is-hidden":false,
	"is-floating":true,
	"is-sticky":false,
	"is-grabbed":false
}

Is this an unintended behavior in yabai, or am I misinterpreting the expected functionality?

macOS version: Sequoia 15.3.1
yabai version: yabai-v7.1.11


Expected Behavior:
Transient system UI elements like the input indicator should not be recognized as standard windows or trigger window-related events.

@Bellavene
Copy link

Bellavene commented Mar 11, 2025

I have not seen such a problem. And later turned it off anyway, using input indication through borders instead.

@kiangti
Copy link
Author

kiangti commented Mar 11, 2025

I have not seen such a problem. And later turned it off anyway, using input indication through borders instead.

I think this input source bubble is really useful because it helps me quickly see which input source I'm using. It’s funny though—I’ve noticed many people actually disable this system feature 😂. However, it can get annoying because every time I switch input sources, yabai triggers window_created and window_destroyed events.

@Bellavene
Copy link

Bellavene commented Mar 24, 2025

Window border color switch is more elegant for tracking input method as for me : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants