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

When Terminal has focus, shift+drag on title bar does not trigger FancyZones #14797

New Issue
Closed
opened 2026-01-31 04:19:46 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 04:19:46 +00:00
Owner
Copy Link

Originally created by @jdmarch on GitHub (Aug 5, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

PowerToys 0.43.0

Steps to reproduce

On a laptop+monitor setup using virtual desktops.
With FancyZones defined for a desktop.

  1. Give the Terminal window focus (by opening it, or click or Alt+Tab on existing Terminal window)

  2. Shift+Left-click+drag on Terminal title. FancyZone borders / highlighted regions do not appear on screen as expected. Window does not move during drag as would be expected with NO shift modifier, but when drag is released, Terminal window moves to new position as if shift had not been pressed (i.e. normal window drag).

  3. Same attempt (shift+drag to FancyZone) on any other (non-Terminal) window. This window snaps to FancyZone as expected.

  4. Same attempt on Terminal window (which no longer has focus). This time, snaps to FancyZone as expected.

  5. Without losing Terminal focus, try again. Fails again.

  6. Give focus to any non-Terminal window.

  7. Without giving Terminal focus, try again on Terminal. Succeeds.

Expected Behavior

Show FancyZone during shift+drag, snap to FancyZone on drag release.

Actual Behavior

Terminal window is unresponsive during shift+drag, moves on drag release.

Originally created by @jdmarch on GitHub (Aug 5, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software PowerToys 0.43.0 ### Steps to reproduce On a laptop+monitor setup using virtual desktops. With FancyZones defined for a desktop. 1) Give the Terminal window focus (by opening it, or click or Alt+Tab on existing Terminal window) 2) Shift+Left-click+drag on Terminal title. FancyZone borders / highlighted regions do not appear on screen as expected. Window does not move during drag as would be expected with NO shift modifier, but when drag is released, Terminal window moves to new position as if shift had not been pressed (i.e. normal window drag). 3) Same attempt (shift+drag to FancyZone) on any other (non-Terminal) window. This window snaps to FancyZone as expected. 4) Same attempt on Terminal window (which no longer has focus). This time, snaps to FancyZone as expected. 5) Without losing Terminal focus, try again. Fails again. 6) Give focus to any non-Terminal window. 7) Without giving Terminal focus, try again on Terminal. Succeeds. ### Expected Behavior Show FancyZone during shift+drag, snap to FancyZone on drag release. ### Actual Behavior Terminal window is unresponsive during shift+drag, moves on drag [release.](url)
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 04:19:46 +00:00
claunia commented 2026-01-31 04:19:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2021):

This is a dupe of #2905, which is actually a dupe of microsoft/PowerToys#209.

WAIT but that was fixed in 2019. So this must be some new regression. I'd follow up with PowerToys on their repo: https://github.com/microsoft/PowerToys/issues

@zadjii-msft commented on GitHub (Aug 5, 2021): ~~This is a dupe of #2905, which is actually a dupe of microsoft/PowerToys#209.~~ WAIT but that was fixed in 2019. So this must be some new regression. I'd follow up with PowerToys on their repo: https://github.com/microsoft/PowerToys/issues
claunia commented 2026-01-31 04:19:47 +00:00
Author
Owner
Copy Link

@jdmarch commented on GitHub (Aug 5, 2021):

Thanks @zadjii-msft -- While that was indeed fixed / closed, there were subsequent reports on that issue, which were referred to https://github.com/microsoft/PowerToys/issues/1466, which was labeled as Resolution-External. So ¯\_(ツ)_/¯

@jdmarch commented on GitHub (Aug 5, 2021): Thanks @zadjii-msft -- While that was indeed fixed / closed, there were subsequent reports on that issue, which were referred to https://github.com/microsoft/PowerToys/issues/1466, which was labeled as `Resolution-External`. So `¯\_(ツ)_/¯`
claunia commented 2026-01-31 04:19:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2021):

@crutkas can we get more context on this from the PowerToys side? I thought y'all took a fix for PT for the Terminal, but both microsoft/PowerToys#1466 and microsoft/PowerToys#209 are just kind of black hole issues right now, without any real guidance on why the Terminal doesn't work in this case. Is this a XAML Islands thing?

I'd rather get to the root cause of the issue (even if it's unsolvable) than just spiderman.png all day.

@zadjii-msft commented on GitHub (Aug 5, 2021): @crutkas can we get more context on this from the PowerToys side? I thought y'all took a fix for PT for the Terminal, but both microsoft/PowerToys#1466 and microsoft/PowerToys#209 are just kind of black hole issues right now, without any real guidance on why the Terminal doesn't work in this case. Is this a XAML Islands thing? I'd rather get to the root cause of the issue (even if it's unsolvable) than just [spiderman.png](https://i.kym-cdn.com/entries/icons/original/000/023/397/C-658VsXoAo3ovC.jpg) all day.
claunia commented 2026-01-31 04:19:47 +00:00
Author
Owner
Copy Link

@crutkas commented on GitHub (Aug 6, 2021):

@zadjii-msft Ive gone into depth how to recreate the issue without FZ/ PT even installed in other bugs here. We amplify the issue since the behavior required for FZ.

Best of my knowledge we did not do a fix for it. I'd sync internal as I'm OOF until September 1 also.

@crutkas commented on GitHub (Aug 6, 2021): @zadjii-msft Ive gone into depth how to recreate the issue without FZ/ PT even installed in other bugs here. We amplify the issue since the behavior required for FZ. Best of my knowledge we did not do a fix for it. I'd sync internal as I'm OOF until September 1 also.
claunia commented 2026-01-31 04:19:48 +00:00
Author
Owner
Copy Link

@xg5-simon commented on GitHub (Aug 3, 2025):

Exact same behavior still happening on v0.92.1

@xg5-simon commented on GitHub (Aug 3, 2025): Exact same behavior still happening on v0.92.1
claunia commented 2026-01-31 04:19:48 +00:00
Author
Owner
Copy Link

@SeaRedm commented on GitHub (Jan 13, 2026):

Still an issue on the latest version for me also / windows 11 enterprise Release v0.96.1 / powershell 7

@SeaRedm commented on GitHub (Jan 13, 2026): Still an issue on the latest version for me also / windows 11 enterprise Release v0.96.1 / powershell 7
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 Needs-Tag-Fix Needs-Triage Resolution-External
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#14797
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?