[jmacato]

What does the pull request do?

Adds AutomationPeer.ToScreen(Rect) so each peer converts its own bounding rectangle to screen coordinates, and uses it from the Win32 UIA backend.

What is the current behavior?

AutomationNode.GetBoundingRectangle only produces bounds when the visual root peer is a ControlAutomationPeer with a live Control owner:

if (Peer.GetVisualRoot() is ControlAutomationPeer root &&
    root.Owner.GetPresentationSource() is not null)
    ...

Any custom IRootProvider that is not a ControlAutomationPeer (embedded/hosted trees) fails that check and every element reports an empty rectangle. The conversion also goes through root.Owner (the FocusRoot), while GetBoundingRectangle returns rects relative to the visual root, so the two disagree whenever FocusRoot is offset from the root.

What is the updated/expected behavior with this PR?

Bounds are correct for any root provider. The peer converts its own rectangle in the coordinate space it was measured in, so there is no root-peer type requirement and no FocusRoot offset.

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

None. ToScreen is additive and [PrivateApi].

[MrJul]

LGTM!

[avaloniaui-bot]

You can test this PR using the following package version. 12.1.999-cibuild0067306-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]