-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Maximization takes three steps for Chrome #3277
Comments
see comments in the issues above. On my end this was caused by the Grammarly Desktop app. Quit it and restart Chrome. |
Thanks for pointing to those comments. I tried to make sure all other apps were killed but got the same behaviour. Even in the incognito mode with all the extensions disabled, getting the same behaviour. Getting the same behaviour with Microsoft Edge. Firefox like other apps is working fine. Also running Karabiner elements but suspecting it has something to do with Chromium-based browsers. |
This may help... I use this vor maximising windows. function maximizeWindow()
-- full screen window
local win = hs.window.focusedWindow()
local f = win:frame()
local screen = win:screen()
local max = screen:frame()
f.x = max.x
f.y = max.y
f.w = max.w
f.h = max.h
win:setFrame(f,0)
end |
Thanks @dasmurphy Get the same issue with your routine. Everything except Chrome and Edge works fine. |
@hasantahir That is weird, since Chrome is working with this routine here fine. |
FWIW, I am experiencing these same symptoms (and not just for Edit: Removed lists of applications I observed to be affected and not affected, as this appears to be a red herring based on further experimentation. I've found one reliable way to reproduce this issue. Turning on the Accessibility Keyboard appears to cause any application that becomes active while it is present to become poisoned with this sluggish window manipulation behavior ( Disable the Accessibility Keyboard, restart the poisoned apps, and window manipulation returns to normal. From all of the issues I've read touching on this problem, it appears that the Accessibility Keyboard may be only one possible trigger for this behavior. That said, I have not been able to reproduce the issue with 1Password (8.9.4), the "Follow keyboard focus" accessibility feature, the "Use keyboard shortcuts to zoom" accessibility feature, or any other accessibility feature (I went through trying many of them). I'm on macOS |
Looks like this is probably an issue with the |
I get the same issue with following environment.
|
Getting this on Sonoma with Firefox too. |
As reported earlier in #2578, I notice that the Chrome app window takes three steps to maximize. For the rest of the apps,
hs.window:maximize()
works fine.I have been using
hs.window.focusedWindow():maximize()
tied to the keyboard shortcut⌘ + ⌥ + ⌃ + M
to maximise the windows.Below is a screencast of what I observed:
hammerspoon.mp4
Cheers
The text was updated successfully, but these errors were encountered: