Skip to content
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

Pressing keyboard up-arrow maximizes app to full screen (sometimes) #855

Open
ew98 opened this issue Dec 15, 2021 · 5 comments · May be fixed by #868
Open

Pressing keyboard up-arrow maximizes app to full screen (sometimes) #855

ew98 opened this issue Dec 15, 2021 · 5 comments · May be fixed by #868

Comments

@ew98
Copy link

ew98 commented Dec 15, 2021

Not sure where the focus is but it must be out of any tiled SSH session. I usually work with anywhere from 2 to 6 tiles, each with multiple tabs, all SSH. When focus is inside any of the tiled sessions, up arrow is interpreted by my shell and responds as expected. From time to time, focus must be somewhere on the app but not within a session. In that case, the up arrow maximizes the app window to full screen. This was not happening in 1.4.0.9.

I've seen this multiple times but cannot reproduce at will. Don't know what window state for the app triggers the behavior.

  • OS: Windows 10 enterprise
  • Browser Brave
  • Version: 1.4.0.10
@jimradford
Copy link
Owner

Please let me know if you can reliably reproduce this issue so I can look into it further.

@oopoopoop
Copy link

oopoopoop commented Apr 21, 2022

Please confirm if these steps can also reliably reproduce the issue for you:

  1. WindowsKey + L to lock Windows
  2. Ctrl+Alt+Del to login
  3. refocus on SuperPuTTY (Alt-Tab or mouse click)
  4. press up-arrow

@dofuuz
Copy link

dofuuz commented Apr 27, 2022

To reproduce this issue with Win+L, you have to press arrow key other than ↑ when SuperPutty is already maximized.

Pressing arrow key is triggering same behavior with Win+→, Win+←, Win+↑, Win+↓.

@oopoopoop
Copy link

Oh, another prerequisite is that you'll need at least a session open for this bug to kick-in. It doesn't have to be connected though, but an empty SuperPuTTY (fresh launched) just won't cut it.

@dofuuz
Copy link

dofuuz commented May 2, 2022

I used git-bisect to find the commit that introduced this bug. And it is 9cf0816.

@dofuuz dofuuz linked a pull request May 18, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants