Skip to content

fix(cua-driver): clarify Windows window-state coordinates - #3265

Draft
ethanblake4 wants to merge 1 commit into
trycua:mainfrom
ethanblake4:windows-coordinate-contract
Draft

fix(cua-driver): clarify Windows window-state coordinates#3265
ethanblake4 wants to merge 1 commit into
trycua:mainfrom
ethanblake4:windows-coordinate-contract

Conversation

@ethanblake4

@ethanblake4 ethanblake4 commented Aug 19, 2026

Copy link
Copy Markdown

Summary: exposes window-relative bounds and screenshot-to action transform for window-relative cua calls (as opposed to current alwaysscreen-relative bounds). Also, excludes UIA rectangles that lie completely outside the window bounds (this was a case I came across in a real app). Validation: cargo test -p platform-windows window_state_coordinates --lib; cargo check -p platform-windows; cargo check -p cua-driver; cargo fmt --all -- --check; git diff --check. Known gap: the generic live protocol test selected an unrelated IslandWindow whose provider hit the existing four-second UIA timeout before structured output.

@ethanblake4

Copy link
Copy Markdown
Author

I'm leaving this as draft; it does significantly improve performance on certain scenarios for me, but it seems like a broader architectural change that would need to be applied across platforms which I don't have the capacity for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants