-
-
Notifications
You must be signed in to change notification settings - Fork 664
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
A random window becomes "always-on-bottom" frequently #2531
Comments
I'm concerned by the |
Well, this issue makes yabai plain unusable because after swapping few window around, the issue is reproduced and I have to restart the apps. Almost every time. |
I'll look into this when I have time. I think the auto-move because of space destroy is a key thing here. For now you can use The intended purpose of the feature is to keep floating windows always on top of tiled/managed windows. |
The workaround helps, thank you for the suggestion and for the awesome software :) I want to add one more step necessary to reproduce the issue -- before the step 1 from above, it seems necessary to switch the layout mode to bsp and back to float. Then the issue is reproduced reliably for me. |
yabai-v7.1.6
After a period of normal usage (creating spaces, moving/swapping windows around), any random window can occasionally become "always-on-bottom", which is exactly the opposite of "always-on-top" (for the lack of better term). Meaning it is always hidden behind any other window on top of it. The only solution is to quit and restart the app that is drawing this window.
I don't see any errors in the log.
I haven't found reliable steps to reproduce it, but it happens about every ~15 minutes of normal usage. I don't have any obvious toggles that can do that in my rc files (attached). I'm happy to collect any data about the window if needed.
skhdrc.txt
yabairc.txt
UPD: Just reproduced the issue as follows:
I can now focus the said window from the mission control, but it's always covered by other windows.
Here's the query for the window after reproducing the issue:
The text was updated successfully, but these errors were encountered: