Feature Request: Fix Accessibility BoundingRects for TextRanges

[carlos-zamora]

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() 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.

[ghost]

🎉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
• Store Download