Skip to content

docs(cua-driver): correct CoreWindow/Calculator section in autostart.mdx - #1608

Merged
f-trycua merged 1 commit into
mainfrom
docs/cua-driver-uia-corewindow-corrections
May 20, 2026
Merged

docs(cua-driver): correct CoreWindow/Calculator section in autostart.mdx#1608
f-trycua merged 1 commit into
mainfrom
docs/cua-driver-uia-corewindow-corrections

Conversation

@f-trycua

@f-trycua f-trycua commented May 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

The autostart.mdx "What it does NOT unlock" section had a wrong architectural claim about Calculator-class apps. The triangulation in #1606 showed the actual pattern: ElementFromHandle on a Windows.UI.Core.CoreWindow HWND returns an empty wrapper, but the real XAML tree is registered at the desktop root as a sibling element with the same ProcessId. cua-driver-rs's UIA enumerator now handles that transparently via the root-walk fallback merged in #1606.

Changes

Test plan

  • pnpm docs:check-links (will be exercised by CI)
  • Vercel preview renders the corrected section

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Enhanced guidance on CoreWindow-class app automation with updated fallback handling explanations
    • Clarified XAML hotkey accelerator limitations and documented UIA tree walk workaround

Review Change Stack

…start.mdx

The "What it does NOT unlock" section had a wrong architectural claim:
that CoreWindow apps like Calculator are unreachable because they have
no addressable HWND. The triangulation done in #1606 (Calculator vs
Settings vs modern Notepad) showed the actual pattern: ElementFromHandle
on a Windows.UI.Core.CoreWindow HWND returns an empty wrapper, but the
real XAML tree is registered at the desktop root as a sibling element
with the same ProcessId. inspect.exe walks from root for these apps;
cua-driver-rs now does the same via the root-walk fallback merged in
#1606.

Replaces the architectural-limit paragraph with:
- A new "CoreWindow-class apps and the UIA root-walk fallback" section
  explaining what the fallback does and linking to #1606
- An updated "What it does NOT unlock" entry that points at the real
  remaining gap: hotkey accelerator shortcuts on XAML targets (#1607),
  with the workaround (UIA tree walk + click on the menu item)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@vercel

vercel Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 20, 2026 2:28pm

Request Review

@f-trycua
f-trycua merged commit 66ea051 into main May 20, 2026
4 of 7 checks passed
@coderabbitai

coderabbitai Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6b0e6b52-0870-42e9-b7c6-1be7f23d3a00

📥 Commits

Reviewing files that changed from the base of the PR and between d8b9021 and 6bd1780.

📒 Files selected for processing (1)
  • docs/content/docs/cua-driver/guide/getting-started/autostart.mdx

📝 Walkthrough

Walkthrough

This PR updates the autostart and UWP automation documentation by expanding the limitations section. It adds a detailed subsection explaining how CoreWindow-class apps (Calculator, Settings, older UWPs) are handled when element queries return no actionable nodes, describes a UIA root-walk fallback behavior, and clarifies hotkey accelerator limitations on XAML targets with a documented workaround.

Changes

CoreWindow UIA Fallback and Hotkey Limitation Documentation

Layer / File(s) Summary
CoreWindow UIA fallback and hotkey limitation clarification
docs/content/docs/cua-driver/guide/getting-started/autostart.mdx
Replaces the previous Calculator-class DirectComposition limitation paragraph with an expanded explanation of CoreWindow-class app handling via UIA root-walk fallback when ElementFromHandle yields no actionable nodes, adds a specific hotkey/accelerator limitation with a UIA menu-item plus click workaround, and includes a tracking reference link.

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • trycua/cua#1606: Implements the CoreWindow-class UIA root-walk fallback behavior in the driver code that this PR documents.
  • trycua/cua#1583: Prior documentation update to the same autostart.mdx file; this PR further refines the limitations section.

Poem

🐰 CoreWindows dance, and fallbacks bloom,
UIA walks through the darkened room,
Hotkeys falter, clicks prevail,
Where docs once failed, our prose now sail!

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/cua-driver-uia-corewindow-corrections

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant