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: Fix Accessibility BoundingRects for TextRanges #2942

New Issue
Closed
opened 2026-01-30 23:09:23 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:09:23 +00:00
Owner
Copy Link

Originally created by @carlos-zamora on GitHub (Jul 25, 2019).

Originally assigned to: @carlos-zamora on GitHub.

Summary of the new feature/enhancement

Thanks to #2083, we now have BoundingRects for text ranges. We can modify them and explore the text buffer properly.

Just one little problem...
image

The BoundingRects aren't actually on the text ranges properly. They update and function correctly, but they should look something like how they do in ConHost:
image

Proposed technical implementation details (optional)

There's a few places in UiaTextRange that use ScreenToClient() and ClientToScreen(); We can use them in ConHost because we have an HWND. Unfortunately, Windows Terminal doesn't have access to an HWND (and it seems like that'll be really hard to do).

XAML, on the other hand, should already know some information about bounding rects. That's how we got the one around the TermControl to appear and all of the other XAML elements.

We need to investigate if/how we can leverage XAML's knowledge of screen bounding rects and just pass them along to the UiaTextRange.

Originally created by @carlos-zamora on GitHub (Jul 25, 2019). Originally assigned to: @carlos-zamora on GitHub. # Summary of the new feature/enhancement Thanks to #2083, we now have BoundingRects for text ranges. We can modify them and explore the text buffer properly. Just one little problem... ![image](https://user-images.githubusercontent.com/11050425/61896035-e9c1df80-aec8-11e9-8578-16d14adb91bb.png) The BoundingRects aren't actually on the text ranges properly. They update and function correctly, but they should look something like how they do in ConHost: ![image](https://user-images.githubusercontent.com/11050425/61896134-28579a00-aec9-11e9-8ff7-99552e54fa9c.png) # Proposed technical implementation details (optional) There's a few places in UiaTextRange that use `ScreenToClient()` and `ClientToScreen();` We can use them in ConHost because we have an HWND. Unfortunately, Windows Terminal doesn't have access to an HWND (and it seems like that'll be really hard to do). XAML, on the other hand, should already know some information about bounding rects. That's how we got the one around the TermControl to appear and all of the other XAML elements. We need to investigate if/how we can leverage XAML's knowledge of screen bounding rects and just pass them along to the UiaTextRange.
claunia commented 2026-01-30 23:09:24 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 27, 2019):

:tada:This issue was addressed in #2423, which has now been successfully released as Windows Terminal Preview v0.4.2382.0.🎉

Handy links:

@ghost commented on GitHub (Aug 27, 2019): :tada:This issue was addressed in #2423, which has now been successfully released as `Windows Terminal Preview v0.4.2382.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.4.2382.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-Feature Needs-Tag-Fix 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#2942
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?