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

Can't move window (no, for real) #15866

New Issue
Open
opened 2026-01-31 04:50:49 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:50:49 +00:00
Owner
Copy Link

Originally created by @seanofw on GitHub (Nov 12, 2021).

Windows Terminal version (or Windows build number)

1.11.2921.0

Other Software

WSL 2

Steps to reproduce

Open Terminal. It mysteriously spawns behind every other window for some reason. Try to drag its around, or close it, or minimize it, or maximize it. None of those actions work unless I click outside its window afterward, and then they happen instantly.

Expected Behavior

Normal window behavior? I can drag it, and it drags. I can close it, and it closes.

Actual Behavior

I turned on my computer this morning (Windows 10.0.19043.1288), and opened a couple of Firefox windows and Discord, and then opened Terminal. Several very strange things happened:

  • First, its window spawns behind every other window. I have to click it to bring it to the foreground, every time. If I close and reopen it, it spawns behind every other window again.
  • Second, I can't drag it. I discovered, though, that in some cases if I clicked outside the tab area to drag it, it would eventually "move," but only after it lost focus -- i.e., after I finished the drag, if I clicked on another window, or the Start Menu, then suddenly it would jump to approximately where I'd dragged it). This only works about half the time, though.
  • Third (and this is super-weird) I started poking at its settings to see if something had changed in it. Opening other tabs (WSL, Powershell, cmd) has no effect on its behavior, but if a Settings tab is open, and only if a Settings tab is open, suddenly the window can be dragged normally! The moment the Settings tab is closed, though, it reverts back to the same non-dragging behavior. Or if I simply click back to the WSL tab, leaving Settings "open" in the background, it stops working again as well.
  • The lack of normal nonclient behavior extends beyond just dragging. If I click the "X" to close it, for example, it doesn't actually close until it loses focus to another window. Same for minimizing or maximizing.

When it spawns, it has only one WSL bash prompt in it. No Powershell, no cmd, nothing else.

I really don't know quite what's going on here: It's as though all nonclient messages are getting batched up when they occur, and then only get delivered when the window loses focus.

It happens really consistently right now. I'm not sure if it'll happen after I reboot Windows, but it started happening on a fresh boot this morning, so it might continue happening after a reboot.

That's all I have. My current workaround for making it usable is to leave a Settings tab open and switch to it whenever I want to drag the window. ¯_(ツ)_/¯

Originally created by @seanofw on GitHub (Nov 12, 2021). ### Windows Terminal version (or Windows build number) 1.11.2921.0 ### Other Software WSL 2 ### Steps to reproduce Open Terminal. It mysteriously spawns behind every other window for some reason. Try to drag its around, or close it, or minimize it, or maximize it. None of those actions work unless I click _outside_ its window afterward, and then they happen instantly. ### Expected Behavior Normal window behavior? I can drag it, and it drags. I can close it, and it closes. ### Actual Behavior I turned on my computer this morning (Windows 10.0.19043.1288), and opened a couple of Firefox windows and Discord, and then opened Terminal. Several very strange things happened: - First, its window spawns _behind_ every other window. I have to click it to bring it to the foreground, every time. If I close and reopen it, it spawns _behind_ every other window again. - Second, I can't drag it. I discovered, though, that in some cases if I clicked outside the tab area to drag it, it would eventually "move," but only _after_ it lost focus -- i.e., after I finished the drag, if I clicked on _another_ window, or the Start Menu, then suddenly it would jump to approximately where I'd dragged it). This only works about half the time, though. - Third (and this is super-weird) I started poking at its settings to see if something had changed in it. Opening other tabs (WSL, Powershell, cmd) has no effect on its behavior, but if a _Settings_ tab is open, and _only_ if a Settings tab is open, suddenly the window can be dragged normally! The moment the Settings tab is closed, though, it reverts back to the same non-dragging behavior. Or if I simply click back to the WSL tab, leaving Settings "open" in the background, it stops working again as well. - The lack of normal nonclient behavior extends beyond just dragging. If I click the "X" to close it, for example, it doesn't actually close until it loses focus to another window. Same for minimizing or maximizing. When it spawns, it has only one WSL bash prompt in it. No Powershell, no cmd, nothing else. I really don't know quite what's going on here: It's as though all nonclient messages are getting batched up when they occur, and then only get delivered when the window loses focus. It happens really consistently right now. I'm not sure if it'll happen after I reboot Windows, but it started happening on a fresh boot this morning, so it might continue happening after a reboot. That's all I have. My current workaround for making it usable is to leave a Settings tab open and switch to it whenever I want to drag the window. ¯\_(ツ)_/¯
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 Area-Input Needs-Author-Feedback Needs-Tag-Fix Needs-Triage Product-Terminal
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#15866
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?