-
-
Notifications
You must be signed in to change notification settings - Fork 662
Dragging Chrome tab causes snapping bug when creating new window #2599
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
Comments
Something is wrong in your .yabairc |
I removed all the codes in .yabairc other than following code but still got the same bug: |
Anyway, something triggers insertion point. I have seen it happen only if something is invoking it through a command to yabai. |
The visual you see is because of interaction with the mouse-drag system: #2109 I'm not fully sure how that would be solved, something like "if active application is Chrome and the mouse is pressed, delay window_created notifications or something. That sounds fairly error prone and pretty terrible to me though, so not sure I want to attempt that. My honest suggestion is to stop using Chrome. It is pretty bad for many reasons these days. |
This seems to be a known issue now, although I just encountered it (I only use Chrome for testing purposes as it's the most popular browser by user share). Maybe it would be worth providing the option to disable |
I also have to use Chrome for work to do certain tasks. A workaround I use is to drag the tab out of the window and release it so it gets titled, then I grab it again. Though it's an extra step, this stops the weird snapping. |
Every time when I am dragging a chrome tab to a new window the dragged window will be snapping back and forth, and when I release my mouse the window won't be at the right place and sometimes leaving a orange overlay behind windows.
Environment
GIF / Screenshot
The text was updated successfully, but these errors were encountered: