Feature Request: Fix Accessibility BoundingRects for TextRanges #2103
Labels
Area-Accessibility
Issues related to accessibility
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Needs-Tag-Fix
Doesn't match tag requirements
Product-Terminal
The new Windows Terminal.
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
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...
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:
Proposed technical implementation details (optional)
There's a few places in UiaTextRange that use
ScreenToClient()
andClientToScreen();
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.
The text was updated successfully, but these errors were encountered: