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

A configuration option to disable tab tearoff is needed. #23554

New Issue
Closed
opened 2026-01-31 08:45:43 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:45:43 +00:00
Owner
Copy Link

Originally created by @feeas on GitHub (Aug 27, 2025).

Description of the new feature

When clicking on a tab, if it moves slightly, Windows Terminal always detaches the tab into a new window, which is rather annoying. I have been struggling with this issue for a long time and hope that an option can be provided to disable tab tearoff.

While searching for solutions, I noticed that others are also struggling with this same issue.
https://www.reddit.com/r/WindowsHelp/comments/1iy1u94/windows_terminal_how_to_prevent_accidentally/

Proposed technical implementation details

No response

Originally created by @feeas on GitHub (Aug 27, 2025). ### Description of the new feature When clicking on a tab, if it moves slightly, Windows Terminal always detaches the tab into a new window, which is rather annoying. I have been struggling with this issue for a long time and hope that an option can be provided to disable tab tearoff. While searching for solutions, I noticed that others are also struggling with this same issue. https://www.reddit.com/r/WindowsHelp/comments/1iy1u94/windows_terminal_how_to_prevent_accidentally/ ### Proposed technical implementation details _No response_
claunia commented 2026-01-31 08:45:46 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 27, 2025):

Presumably this is also an issue with Windows Explorer, right? They use the same tab-row control we do. In that case I'd not be in favor of adding a setting in our app but would rather look forward to an OS-wide fix for this.

@lhecker commented on GitHub (Aug 27, 2025): Presumably this is also an issue with Windows Explorer, right? They use the same tab-row control we do. In that case I'd not be in favor of adding a setting in our app but would rather look forward to an OS-wide fix for this.
claunia commented 2026-01-31 08:45:46 +00:00
Author
Owner
Copy Link

@feeas commented on GitHub (Aug 28, 2025):

Presumably this is also an issue with Windows Explorer, right? They use the same tab-row control we do. In that case I'd not be in favor of adding a setting in our app but would rather look forward to an OS-wide fix for this.

I wasn't aware that Explorer had such an issue. I never use the tab tearoff feature, and even if I need to separate a tab into a new window, the right-click menu already has a 'Move tab to new window' option. The older version of the terminal never supported tab tearoff anyway, so adding a flag to disable this feature should be quite straightforward, right?

@feeas commented on GitHub (Aug 28, 2025): > Presumably this is also an issue with Windows Explorer, right? They use the same tab-row control we do. In that case I'd not be in favor of adding a setting in our app but would rather look forward to an OS-wide fix for this. I wasn't aware that Explorer had such an issue. I never use the tab tearoff feature, and even if I need to separate a tab into a new window, the right-click menu already has a 'Move tab to new window' option. The older version of the terminal never supported tab tearoff anyway, so adding a flag to disable this feature should be quite straightforward, right?
claunia commented 2026-01-31 08:45:49 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 28, 2025):

I know it sounds hilarious coming from a Microsoft employee, but Windows should provide a cohesive experience. Application should look and behave consistent and in a way you'd expect it. If we add this, we add a workaround for something that should not require a workaround to begin with. History has shown that leniency in this regard has always turned out poorly. 1

There are two related registry keys here:

HKEY_CURRENT_USER\Control Panel\Desktop\DragHeight
HKEY_CURRENT_USER\Control Panel\Desktop\DragWidth

We should test if WinUI picks those up. If it doesn't, they should fix that, for accessibility reasons.

  1. Oh, woops no more vertical taskbar. /s (etc.) ↩︎

@lhecker commented on GitHub (Aug 28, 2025): I know it sounds hilarious coming from a Microsoft employee, but Windows should provide a cohesive experience. Application should look and behave consistent and in a way you'd expect it. If we add this, we add a workaround for something that should not require a workaround to begin with. History has shown that leniency in this regard has always turned out poorly. [^1] There are two related registry keys here: ``` HKEY_CURRENT_USER\Control Panel\Desktop\DragHeight HKEY_CURRENT_USER\Control Panel\Desktop\DragWidth ``` We should test if WinUI picks those up. If it doesn't, they should fix that, for accessibility reasons. [^1]: Oh, woops no more vertical taskbar. /s (etc.)
claunia commented 2026-01-31 08:45:49 +00:00
Author
Owner
Copy Link

@feeas commented on GitHub (Aug 29, 2025):

I didn't expect the solution to be so simple. Just by increasing the value to more than 16, the chance of windows separating accidentally is greatly reduced. Even though they still separate sometimes, I feel this is good enough.

@feeas commented on GitHub (Aug 29, 2025): I didn't expect the solution to be so simple. Just by increasing the value to more than 16, the chance of windows separating accidentally is greatly reduced. Even though they still separate sometimes, I feel this is good enough.
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-Feature Needs-Attention Needs-Discussion Needs-Tag-Fix 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#23554
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?