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

UIA in conhost: incorrect word boundaries when text is selected #15950

New Issue
Open
opened 2026-01-31 04:53:11 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 04:53:11 +00:00
Owner
Copy Link

Originally created by @codeofdusk on GitHub (Nov 23, 2021).

Windows Terminal version

Version of OpenConsole included with the wt 1.12 release.

Windows build number

10.0.22000.348

Other Software

NVDA master (2022.1) with UIA.

Steps to reproduce

Paste the following text into a conhost. On my system, this line wraps at the word "upgrade":

tree.IncompatibleFormatError: This file is too new for the currently running version of Treemendous (0.0.0). Please upgrade to Treemendous 42.0.0 or later.

Then:

  • Select a word, such as by moving to the top of the console and searching for the word "please" with CTRL+f.
  • navigate forward in the window by word.

Expected Behavior

word boundaries are correctly calculated: after the wrapping, NVDA says "upgrade", "to", "Treemendous", etc.

Actual Behavior

NVDA reads from the start of the line up to some arbitrary point, can't tell what's going on???

Originally created by @codeofdusk on GitHub (Nov 23, 2021). ### Windows Terminal version Version of OpenConsole included with the wt 1.12 release. ### Windows build number 10.0.22000.348 ### Other Software NVDA master (2022.1) with UIA. ### Steps to reproduce Paste the following text into a conhost. On my system, this line wraps at the word "upgrade": `tree.IncompatibleFormatError: This file is too new for the currently running version of Treemendous (0.0.0). Please upgrade to Treemendous 42.0.0 or later.` Then: * Select a word, such as by moving to the top of the console and searching for the word "please" with CTRL+f. * navigate forward in the window by word. ### Expected Behavior word boundaries are correctly calculated: after the wrapping, NVDA says "upgrade", "to", "Treemendous", etc. ### Actual Behavior NVDA reads from the start of the line up to some arbitrary point, can't tell what's going on???
claunia commented 2026-01-31 04:53:12 +00:00
Author
Owner
Copy Link

@codeofdusk commented on GitHub (Nov 23, 2021):

This does not repro in wt.

CC @carlos-zamora, @DHowett.

@codeofdusk commented on GitHub (Nov 23, 2021): This *does not* repro in wt. CC @carlos-zamora, @DHowett.
claunia commented 2026-01-31 04:53:13 +00:00
Author
Owner
Copy Link

@codeofdusk commented on GitHub (Dec 5, 2021):

Confirmed repro of this issue in FORMATTED conhost, but looks like this is the only remaining word boundary bug!

@codeofdusk commented on GitHub (Dec 5, 2021): Confirmed repro of this issue in `FORMATTED` conhost, but looks like this is the only remaining word boundary bug!
claunia commented 2026-01-31 04:53:13 +00:00
Author
Owner
Copy Link

@codeofdusk commented on GitHub (Dec 5, 2021):

On further testing, it is important that the selected text must be on a line that wraps, and the selection must be somewhere on that line. NVDA+f9/f10 also works for selection here (not just CTRL+f), so I presume the mouse would as well.

@codeofdusk commented on GitHub (Dec 5, 2021): On further testing, it is important that the selected text *must* be on a line that wraps, and the selection must be somewhere on that line. NVDA+f9/f10 also works for selection here (not just CTRL+f), so I presume the mouse would as well.
claunia commented 2026-01-31 04:53:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2021):

This might be related to #5800, or some of the weird line wrapping bugs that I've at least been linking up to that one. I'm thinking particularly the #6901, #10833, #11739 subset.

@zadjii-msft commented on GitHub (Dec 6, 2021): This might be related to #5800, or some of the weird line wrapping bugs that I've at least been linking up to that one. I'm thinking particularly the #6901, #10833, #11739 subset.
claunia commented 2026-01-31 04:53:14 +00:00
Author
Owner
Copy Link

@codeofdusk commented on GitHub (Dec 6, 2021):

@zadjii-msft This bug explicitly doesn't repro in wt (conhost only). Please re-label.

@codeofdusk commented on GitHub (Dec 6, 2021): @zadjii-msft This bug explicitly doesn't repro in wt (conhost *only*). Please re-label.
claunia commented 2026-01-31 04:53:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2021):

.... pretty sure I only added the conhost label...
image
image

@zadjii-msft commented on GitHub (Dec 6, 2021): .... pretty sure I only added the conhost label... ![image](https://user-images.githubusercontent.com/18356694/144871416-1938d012-2bb9-49b9-b420-3e62a1e459a8.png) ![image](https://user-images.githubusercontent.com/18356694/144871526-f88dbae4-f28f-482d-b6a2-ec08ec57f67d.png)
claunia commented 2026-01-31 04:53:14 +00:00
Author
Owner
Copy Link

@codeofdusk commented on GitHub (Dec 6, 2021):

Can't see image but it says you added it to the terminal v2.0 milestone. Should be in 22H1 or whichever milestone tracks the new conhost version post-undocking.

@codeofdusk commented on GitHub (Dec 6, 2021): Can't see image but it says you added it to the terminal v2.0 milestone. Should be in 22H1 or whichever milestone tracks the new conhost version post-undocking.
claunia commented 2026-01-31 04:53:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2021):

Ah. I've been kinda re-thinking how we track milestones for our issues recently, since the Windows-specific ones don't totally make sense and have been pretty loosely tracked, and there's not really a difference between the Terminal and Console backlogs anymore. I suppose for the time being, I'll slap that into the 22H1 milestone, but we might be shaking those up in the future, FYI.

Oh hmm we don't even have a 22H1 milestone, but that makes sense, there isn't a 22H1 milestone internally...

@zadjii-msft commented on GitHub (Dec 6, 2021): Ah. I've been kinda re-thinking how we track milestones for our issues recently, since the Windows-specific ones don't totally make sense and have been pretty loosely tracked, and there's not really a difference between the Terminal and Console backlogs anymore. I suppose for the time being, I'll slap that into the 22H1 milestone, but we might be shaking those up in the future, FYI. Oh hmm we don't even have a 22H1 milestone, but that makes sense, there isn't a 22H1 milestone _internally_...
claunia commented 2026-01-31 04:53:15 +00:00
Author
Owner
Copy Link

@codeofdusk commented on GitHub (May 2, 2022):

FYI this repros in the SV2 inbox console. CC @carlos-zamora, @DHowett.

@codeofdusk commented on GitHub (May 2, 2022): FYI this repros in the SV2 inbox console. CC @carlos-zamora, @DHowett.
claunia commented 2026-01-31 04:53:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 3, 2022):

@codeofdusk Yep, looks like this one didn't make it in unfortunately. Hopefully we'll get a chance for the next release.

@zadjii-msft commented on GitHub (May 3, 2022): @codeofdusk Yep, looks like this one didn't make it in unfortunately. Hopefully we'll get a chance for the next release.
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 Area-Output Help Wanted Issue-Bug Priority-1 Product-Conhost
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#15950
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?