starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal not snapping correctly with the keys Win+Left and Win+Right #19389

New Issue
Closed
opened 2026-01-31 06:41:52 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:41:52 +00:00
Owner
Copy Link

Originally created by @gbr000 on GitHub (Feb 14, 2023).

Windows Terminal version

1.17.1023

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

  1. Open the Terminal
  2. Press Win+Left
  3. Press Win+Right

Expected Behavior

  1. snap to the LEFT side of the screen
  2. snap to the RIGHT side of the screen

Actual Behavior

  1. it snapped to the right side of the screen all in a crazy fashion
  2. it snapped to the left side of the screen all in a crazy fashion

~sometimes it doesn't snap at all, and sometimes this problem doesn't always occur.

I think (but not sure) it only does happen when you leave the terminal opened for hours!

~The problem is recurrent, it happens constantly and in random times

Originally created by @gbr000 on GitHub (Feb 14, 2023). ### Windows Terminal version 1.17.1023 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce 1. Open the Terminal 2. Press Win+Left 3. Press Win+Right ### Expected Behavior 2. snap to the LEFT side of the screen 3. snap to the RIGHT side of the screen ### Actual Behavior 2. it snapped to the right side of the screen all in a crazy fashion 3. it snapped to the left side of the screen all in a crazy fashion ~sometimes it doesn't snap at all, and sometimes this problem doesn't always occur. I think (but not sure) it only does happen when you leave the terminal opened for hours! ~The problem is recurrent, it happens constantly and in random times
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:41:53 +00:00
claunia commented 2026-01-31 06:41:54 +00:00
Author
Owner
Copy Link

@gbr000 commented on GitHub (Feb 14, 2023):

Strangely, press Win+down, then again to minimize the window (the window will hide and without releasing Win all the time), play aroun with the Win key in that minimized state, go LEFT then go up again. Now the snap is inverted.

*NOTE: I could only reproduce this once on my own, but the program automatically starts in that mode when he wanted.

So I could indentify part of the problem but not the cause! Nor the solution!

In that state with the "snaps inverted" also Chrome was inverted for the same period as the Terminal, then once again those return for normal, but it always begun with Terminal, it never happened with all other dozens of applications I have.

My notebook is: AMD 3020e Radeon Vega 3 (Dali) 1.20Ghz, 8GB Ram (Vengeance), SSD NVMe (with 2000 IOPS r/w), 2021 model. Literally the machine is more than fast!

@gbr000 commented on GitHub (Feb 14, 2023): Strangely, press `Win+down`, then again to minimize the window (the window will hide and without releasing `Win` all the time), play aroun with the `Win` key in that minimized state, go LEFT then go up again. Now the snap is inverted. *NOTE: I could only reproduce this once on my own, but the program automatically starts in that mode when he wanted. So I could indentify part of the problem but not the cause! Nor the solution! In that state with the "snaps inverted" also Chrome was inverted for the same period as the Terminal, then once again those return for normal, but it always begun with Terminal, it never happened with all other dozens of applications I have. My notebook is: AMD 3020e Radeon Vega 3 (Dali) 1.20Ghz, 8GB Ram (Vengeance), SSD NVMe (with 2000 IOPS r/w), 2021 model. Literally the machine is more than fast!
claunia commented 2026-01-31 06:41:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 15, 2023):

Hey, would you be able to take videos/screenshots of what's happening? I'm having trouble visualizing it.

Thanks!

@DHowett commented on GitHub (Feb 15, 2023): Hey, would you be able to take videos/screenshots of what's happening? I'm having trouble visualizing it. Thanks!
claunia commented 2026-01-31 06:41:55 +00:00
Author
Owner
Copy Link

@gbr000 commented on GitHub (Feb 16, 2023):

I cannot reproduce it all the time but it happens when I don't want it. (I'm investigating the reason why)

Most of the times happened after leaving the Terminal opened for hours like 3 to 6 hours (and maybe after I reopen/close the lid?)

I just updated the Windows 10, maybe it was a Windows problem rather than Terminal, for now there's no problems. I'm thinking about upgrade to Win 11.

*I cannot reproduce this error when I want, but it happens in random times, basically when you press Win+Left the window goes right, it gets inversed horizontally (not verically) and the windows as a confused state (What I have noticed is that when the windows is at that state it gets a little off position on the screen when is inverted but not when it's normal). And it's possible to fix that inversion by pressing Win+arrow keys multiple times, also in that state it's possible to go back to inversion by pressing Win+arrow keys multiple times. But to get to that state I cannot! After Windows is restarted everything goes back to normal!

state = time when the bug occurs!

@gbr000 commented on GitHub (Feb 16, 2023): I cannot reproduce it all the time but it happens when I don't want it. (I'm investigating the reason why) Most of the times happened after leaving the Terminal opened for hours like 3 to 6 hours (and maybe after I reopen/close the lid?) I just updated the Windows 10, maybe it was a Windows problem rather than Terminal, for now there's no problems. I'm thinking about upgrade to Win 11. *I cannot reproduce this error when I want, but it happens in random times, basically when you press `Win+Left` the window goes right, it gets inversed horizontally (not verically) and the windows as a confused state (What I have noticed is that when ***the windows*** is at that state it gets a little off position on the screen when is inverted but not when it's normal). And it's possible to fix that inversion by pressing `Win+arrow keys` multiple times, also in that state it's possible to go back to inversion by pressing `Win+arrow keys` multiple times. But to get to that state I cannot! After Windows is restarted everything goes back to normal! state = time when the bug occurs!
claunia commented 2026-01-31 06:41:55 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 22, 2023):

Thanks @gbr000! We're going to close this bug since we can't get a consistent repro on it. If this happens again, please take a screenshot so we can investigate it further. Thanks!

@carlos-zamora commented on GitHub (Feb 22, 2023): Thanks @gbr000! We're going to close this bug since we can't get a consistent repro on it. If this happens again, please take a screenshot so we can investigate it further. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19389
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?