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

Clicking on window without dragging causes a selection #3706

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

Originally created by @Molanda on GitHub (Sep 2, 2019).

Environment

Windows build number: 10.0.18362.295
Windows Terminal version (if applicable): 0.4.2382.0

Steps to reproduce

Click on the terminal window without dragging.

Expected behavior

This should clear any existing selection but not create a new one. This is consistent with other Windows programs which only show a selection when the cursor is dragged.

Actual behavior

A character is selected.

Originally created by @Molanda on GitHub (Sep 2, 2019). # Environment ```none Windows build number: 10.0.18362.295 Windows Terminal version (if applicable): 0.4.2382.0 ``` # Steps to reproduce Click on the terminal window without dragging. # Expected behavior This should clear any existing selection but not create a new one. This is consistent with other Windows programs which only show a selection when the cursor is dragged. # Actual behavior A character is selected.
claunia added the Resolution-By-DesignNeeds-Tag-Fix labels 2026-01-30 23:27:59 +00:00
claunia commented 2026-01-30 23:28:00 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 3, 2019):

Today, this is by design. We don't act like other Windows applications that emit text because they have a selection caret, and we don't. We've been talking about the right behavior here for a while, and we decided that in the "default" configuration we'd match the existing console, which does work like this.

We recently added copyOnSelect which, while it does add the eponymous copy-on-select, also suppresses single-character selection (you must click and drag to another cell before selection begins.)

I'm going to mark this one by-design for now. Thanks/sorry!

@DHowett-MSFT commented on GitHub (Sep 3, 2019): Today, this is by design. We don't act like other Windows applications that emit text because they have a _selection caret_, and we don't. We've been talking about the right behavior here for a while, and we decided that in the "default" configuration we'd match the existing console, which does work like this. We recently added `copyOnSelect` which, while it does add the eponymous copy-on-select, also suppresses single-character selection (you must click and drag to another cell before selection begins.) I'm going to mark this one by-design for now. Thanks/sorry!
claunia commented 2026-01-30 23:28:00 +00:00
Author
Owner
Copy Link

@Molanda commented on GitHub (Sep 3, 2019):

Thank you for your response. I understand the current decision, but would like to add some additional details for consideration.

  • Not all application that emit text have a selection caret. The most notable example is the web browser (excluding form fields). If you click on text in a browser, no selection happens unless you also drag. PuTTY is another example where a drag is required to select.
  • If anything, creating a block on click gives the false visual impression that the cursor has been moved.
  • The existing console has the ability to turn off QuickEdit mode.
  • While the behavior matches the existing console, it really offers no value. If someone clicks the window to the front, their next move is extremely unlikely to be to copy the random character that is now selected.

I will try the copy-on-select once released (I have the build from the Microsoft Store).

@Molanda commented on GitHub (Sep 3, 2019): Thank you for your response. I understand the current decision, but would like to add some additional details for consideration. - Not all application that emit text have a _selection caret_. The most notable example is the web browser (excluding form fields). If you click on text in a browser, no selection happens unless you also drag. PuTTY is another example where a drag is required to select. - If anything, creating a block on click gives the false visual impression that the cursor has been moved. - The existing console has the ability to turn off _QuickEdit_ mode. - While the behavior matches the existing console, it really offers no value. If someone clicks the window to the front, their next move is extremely unlikely to be to copy the random character that is now selected. I will try the copy-on-select once released (I have the build from the Microsoft Store).
claunia commented 2026-01-30 23:28:01 +00:00
Author
Owner
Copy Link

@garth commented on GitHub (Nov 28, 2019):

it really offers no value

I could not agree more with this observation. This needs to be an option. eg 'selectOnClick'?

@garth commented on GitHub (Nov 28, 2019): > it really offers no value I could not agree more with this observation. This needs to be an option. eg 'selectOnClick'?
claunia commented 2026-01-30 23:28:01 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 28, 2019):

For what it's worth, I agree. Selection is a charged topic, though, as we've well seen.

If you enable copyOnSelect, terminal disables single-character selection. If that's an acceptable compromise, we can leave it at that and evaluate more robust selection settings as we go forward. 😄

@DHowett-MSFT commented on GitHub (Nov 28, 2019): For what it's worth, I agree. Selection is a charged topic, though, as we've well seen. If you enable `copyOnSelect`, terminal disables single-character selection. If that's an acceptable compromise, we can leave it at that and evaluate more robust selection settings as we go forward. :smile:
claunia commented 2026-01-30 23:28:01 +00:00
Author
Owner
Copy Link

@ryanmortier commented on GitHub (Apr 16, 2020):

This is such a terrible user experience.

@ryanmortier commented on GitHub (Apr 16, 2020): This is such a terrible user experience.
claunia commented 2026-01-30 23:28:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 16, 2020):

Thanks for your feedback. It's a good thing we fixed it in #5096.

@DHowett-MSFT commented on GitHub (Apr 16, 2020): Thanks for your feedback. It's a good thing we fixed it in #5096.
claunia commented 2026-01-30 23:28:02 +00:00
Author
Owner
Copy Link

@Molanda commented on GitHub (Apr 16, 2020):

Awesome news!

@Molanda commented on GitHub (Apr 16, 2020): Awesome news!
claunia commented 2026-01-30 23:28:02 +00:00
Author
Owner
Copy Link

@ryanmortier commented on GitHub (Apr 16, 2020):

This is great news, thanks so much.

@ryanmortier commented on GitHub (Apr 16, 2020): This is great news, thanks so much.
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 Resolution-By-Design
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#3706
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?