Implement actionability checks in robocorp.windows actions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 653
- Forks
- 108
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Description
Target components
windows
Why & who
Unconditional clicks and inputs lead to unreliable automation and hidden UI errors. Validation of visibility, enabled state, and modal obstruction would make Windows automations safer, more predictable, and easier to debug.
This affects Robocorp developers building Windows automations, especially those used to Playwright-style reliability and explicit error handling.
Feature or enhancement
When automating Windows apps, robocorp.windows executes clicks even if a modal or other overlay blocks the target. It should instead validate interactability before acting—similar to Playwright or pywinauto.verify_actionable()—and raise a clear exception or timeout when the element is not actionable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the robocorp.windows actions under the windows target component and review how clicks and inputs are currently executed. Compare the desired checks with Playwright actionability and pywinauto.verify_actionable(); done means blocked, invisible, or disabled targets produce a clear exception or timeout instead of acting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100