You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AeroSpace should delay new window detection until the mouse is up. It will help with apps that allow dragging their tabs out to create new windows. Right now, the experience is sluggish when you try to drag tab out of Google Chrome
Noticeable apps: Google Chrome, Brave
Google Chrome and Brave dragged tabs also don't have fullscreen button for the time of new window detection. In case of Brave, it leads to Brave dragged tabs/windows being detected as floating by default: #340
In case of Chrome, there is a hack in AeroSpace the source code that tiles all Chrome windows regardless of the fullscreen button, which leads to other problems: #246#933
The approach with delaying new windows detection until the mouse is up will help to resolve all these problems
The text was updated successfully, but these errors were encountered:
nikitabobko
changed the title
Delay new window detection until the mouse is up (e.g. Google Chrome tab drag)
Delay new window detection until mouse is up (e.g. Google Chrome tab drag)
Jan 18, 2025
AeroSpace should delay new window detection until the mouse is up. It will help with apps that allow dragging their tabs out to create new windows. Right now, the experience is sluggish when you try to drag tab out of Google Chrome
Noticeable apps: Google Chrome, Brave
Google Chrome and Brave dragged tabs also don't have fullscreen button for the time of new window detection. In case of Brave, it leads to Brave dragged tabs/windows being detected as floating by default: #340
In case of Chrome, there is a hack in AeroSpace the source code that tiles all Chrome windows regardless of the fullscreen button, which leads to other problems: #246 #933
The approach with delaying new windows detection until the mouse is up will help to resolve all these problems
The text was updated successfully, but these errors were encountered: