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

Incorrect behaviour of UIA IUIAutomationTextRange::Select #11050

New Issue
Closed
opened 2026-01-31 02:37:12 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 02:37:12 +00:00
Owner
Copy Link

Originally created by @codeofdusk on GitHub (Oct 16, 2020).

From the docs:

If the Select method is called on a text range object that represents a degenerate (empty) text range, the text insertion point moves to the starting endpoint of the text range.

Most Braille displays have cursor routing keys above each cell for efficiently moving the caret. NVDA relies on this behaviour of the select method on UTRs to allow Braille users to navigate.

Cc @carlos-zamora, @mehgcap.

Originally created by @codeofdusk on GitHub (Oct 16, 2020). From [the docs](https://docs.microsoft.com/en-us/windows/win32/api/uiautomationclient/nf-uiautomationclient-iuiautomationtextrange-select): > If the Select method is called on a text range object that represents a degenerate (empty) text range, the text insertion point moves to the starting endpoint of the text range. Most [Braille displays](https://en.wikipedia.org/wiki/Refreshable_braille_display) have cursor routing keys above each cell for efficiently moving the caret. NVDA relies on this behaviour of the `select` method on UTRs to allow Braille users to navigate. Cc @carlos-zamora, @mehgcap.
claunia added the Product-ConhostResolution-By-DesignIssue-BugArea-Accessibility labels 2026-01-31 02:37:12 +00:00
claunia commented 2026-01-31 02:37:13 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 16, 2020):

Hmm... This is interesting. This seems to be another problem with comparing how text editors work vs how a terminal works. When a degenerate range is selected on a text editor, the insertion point (cursor) is the position of the degenerate range. But on a terminal, the insertion point is always the prompt at the bottom.

I don't think we can change the behavior of GetSelection() because this is the only way to get the cursor position. But on the other hand, Braille clearly relies on this because they're making degenerate selections. Would it be possible for Braille to expand by character to properly highlight the word letter you're on?

@carlos-zamora commented on GitHub (Oct 16, 2020): Hmm... This is interesting. This seems to be another problem with comparing how text editors work vs how a terminal works. When a degenerate range is selected on a text editor, the insertion point (cursor) is the position of the degenerate range. But on a terminal, the insertion point is always the prompt at the bottom. I don't think we can change the behavior of `GetSelection()` because this is the only way to get the cursor position. But on the other hand, Braille clearly relies on this because they're making degenerate selections. Would it be possible for Braille to expand by character to properly highlight the word letter you're on?
claunia commented 2026-01-31 02:37:14 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 16, 2020):

Discussed offline. The issue described is by design. GetSelection() when there is no selection is expected to return the prompt insertion point. Unlike text editors, if you create a degenerate range earlier in the prompt, then GetSelection(), nothing is expected to happen. This is the equivalent of a sighted user clicking on an editable portion of the prompt. The cursor does not change position.

@carlos-zamora commented on GitHub (Oct 16, 2020): Discussed offline. The issue described is by design. `GetSelection()` when there is no selection is expected to return the prompt insertion point. Unlike text editors, if you create a degenerate range earlier in the prompt, then `GetSelection()`, nothing is expected to happen. This is the equivalent of a sighted user clicking on an editable portion of the prompt. The cursor does not change position.
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-Accessibility Issue-Bug Product-Conhost 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#11050
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?