-
Notifications
You must be signed in to change notification settings - Fork 920
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
SimpleFullscreen on macOS does not get risized when moving window across screens #1118
Comments
It looks like the window bounds are only set upon the initial |
That said, I would strongly prefer applications to not use the simple fullscreen functionality. The simple fullscreen mode prevents the user from using some gestures common to fullscreen applications (i.e. three-finger swipe left or right to go back to the desktop). This is because it is not in fact a fullscreen window, but a regular window with its decorations hidden. It's generally just not what users are expecting from a fullscreen application. I would love to hear about the use-cases for it, because I'm confused as to why anyone would want this behaviour. |
@aleksijuvani Hi, I'm the original reporter from the Alacritty bug. I prefer this mode with Alacritty, as opposed to the Native Fullscreen, because its faster and more convenient to use.
I used the same setup with iTerm2, where I would additionally use the |
I never use native full screens. There is no shortcut for them, unlike with spaces where you can have |
This was reported to Alacritty in alacritty/alacritty#2741.
It seems like the simple fullscreen mode on macOS always keeps the window at the same size, even after it is moved between screens.
The expectation here is that when moving the window, it should take all of the space available on the new monitor, instead of sticking to the old size.
Toggling simple fullscreen after the window has been moved fixes this issue.
The text was updated successfully, but these errors were encountered: