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

Feature Request: The Terminal window's resize border is too small #1517

New Issue
Closed
opened 2026-01-30 22:29:23 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 22:29:23 +00:00
Owner
Copy Link

Originally created by @rkeithhill on GitHub (Jun 4, 2019).

Summary of the new feature/enhancement

You have to have good precision with your mouse to drag resize the window because the resize area is only a couple of pixels wide. This makes for a frustrating experience when you attempt to drag resize the window.

Proposed technical implementation details (optional)

Do what the current conshost window does. It provides somewhere between a 6-8 pixel width drag resize area.

Originally created by @rkeithhill on GitHub (Jun 4, 2019). # Summary of the new feature/enhancement You have to have good precision with your mouse to drag resize the window because the resize area is only a couple of pixels wide. This makes for a frustrating experience when you attempt to drag resize the window. # Proposed technical implementation details (optional) Do what the current conshost window does. It provides somewhere between a 6-8 pixel width drag resize area.
claunia commented 2026-01-30 22:29:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 4, 2019):

:laughing_crying:

We've just had a two hour meeting about window styling and input, and this came up quite a bit during it. I think we have a plan to solve this though, so that's good!

@zadjii-msft commented on GitHub (Jun 4, 2019): :laughing_crying: We've just had a two hour meeting about window styling and input, and this came up quite a bit during it. I think we have a plan to solve this though, so that's good!
claunia commented 2026-01-30 22:29:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 7, 2019):

@bitcrazed assures me he's notified the right people to help us get this fixed :)

@zadjii-msft commented on GitHub (Jun 7, 2019): @bitcrazed assures me he's notified the right people to help us get this fixed :)
claunia commented 2026-01-30 22:29:25 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Jul 2, 2019):

#929 Fixes this!

@cinnamon-msft commented on GitHub (Jul 2, 2019): #929 Fixes this!
claunia commented 2026-01-30 22:29:25 +00:00
Author
Owner
Copy Link

@glen-84 commented on GitHub (Jul 6, 2019):

@cinnamon-msft Shouldn't this issue remain open until there's a release?

@glen-84 commented on GitHub (Jul 6, 2019): @cinnamon-msft Shouldn't this issue remain open until there's a release?
claunia commented 2026-01-30 22:29:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 6, 2019):

Our policy is that bugs are closed when the change that fixes them reaches master. We use the “fix available” and “fix committed” tags to track a fixed bug’s progress to release.

@DHowett-MSFT commented on GitHub (Jul 6, 2019): Our policy is that bugs are closed when the change that fixes them reaches `master`. We use the “fix available” and “fix committed” tags to track a fixed bug’s progress to release.
claunia commented 2026-01-30 22:29:26 +00:00
Author
Owner
Copy Link

@glen-84 commented on GitHub (Jul 6, 2019):

If they have the latest release, and there are no open issues regarding a bug, users may submit duplicates.

Anyway, just a thought. 🙂

@glen-84 commented on GitHub (Jul 6, 2019): If they have the latest release, and there are no open issues regarding a bug, users may submit duplicates. Anyway, just a thought. 🙂
claunia commented 2026-01-30 22:29:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 6, 2019):

People do that regardless of whether we close bugs or leave them open. Or even pin them!

@DHowett-MSFT commented on GitHub (Jul 6, 2019): People do that regardless of whether we close bugs or leave them open. Or even pin them!
claunia commented 2026-01-30 22:29:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 7, 2019):

(Also, thanks for the feedback! We appreciate it. We may want to think a bit more on how we communicate upcoming features and fixes.)

@DHowett-MSFT commented on GitHub (Jul 7, 2019): (Also, thanks for the feedback! We appreciate it. We may want to think a bit more on how we communicate upcoming features and fixes.)
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-UserInterface Issue-Task Product-Terminal Resolution-Fix-Committed
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#1517
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?