[UI-71923] Add UIA hint for interaction that remounts its target - #2105
Conversation
When an interaction (click-before-typing, a click that expands a dropdown/popup) makes the app remount the target as a new node, an activity that resolved the old node faults with "UI element is invalid". Increasing delay or changing input mode does not help — it is a re-resolution problem. Fix: split into separate activities so the second re-resolves its target. Add a "Debugging a failed interaction with an element" section to uia-elements-interaction-guide.md and a one-line pointer to it from ui-automation-guide.md's Common UIA Pitfalls. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Claude finished @liviusanduuip's task in 1m 51s —— View job PR Review: docs(uipath-rpa): add UIA hint for interaction that remounts its target
SummaryAdds a debugging hint for a UIA failure mode where an interaction remounts its target DOM node, causing a stale-node fault. The content is split correctly: a terse pitfall pointer in Change-by-Change Review1.
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | No frontmatter changes |
| E2E Tests | OK | Documentation-only change, no new CLI workflows or commands |
| Skill Body | OK | SKILL.md not modified |
| References & Assets | OK | New section correctly placed; link resolves; pointer discipline followed |
| Repo Hygiene | OK | No secrets, no cross-skill refs, changes scoped to uipath-rpa |
Issues for Manual Review
- Domain accuracy: The remount-on-focus / click-before-typing failure mode described is based on real UIA behavior — but the reviewer should confirm that
TypeInto's built-in click-before-typing is indeed a documented compound action that resolves the target only once (not twice). This is a domain-specific claim the automated review cannot verify.
Conclusion
Clean PR. The content is well-structured, follows the reference pointer discipline, respects the UIA boundary rules, and adds genuine diagnostic value for a failure mode that agents struggle with. The only finding is a cosmetic "though" → "even though" wording nit (Low severity). Approve.
|
/cherrypick release/v1.197 UI-71923 |
|
/cherrypick release/v1.198 UI-71923 |
|
A cherry pick from this PR targeting |
|
A cherry pick from this PR targeting |
|
|
|
|
…et (#2105) When an interaction (click-before-typing, a click that expands a dropdown/popup) makes the app remount the target as a new node, an activity that resolved the old node faults with "UI element is invalid". Increasing delay or changing input mode does not help — it is a re-resolution problem. Fix: split into separate activities so the second re-resolves its target. Add a "Debugging a failed interaction with an element" section to uia-elements-interaction-guide.md and a one-line pointer to it from ui-automation-guide.md's Common UIA Pitfalls. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…et (#2105) When an interaction (click-before-typing, a click that expands a dropdown/popup) makes the app remount the target as a new node, an activity that resolved the old node faults with "UI element is invalid". Increasing delay or changing input mode does not help — it is a re-resolution problem. Fix: split into separate activities so the second re-resolves its target. Add a "Debugging a failed interaction with an element" section to uia-elements-interaction-guide.md and a one-line pointer to it from ui-automation-guide.md's Common UIA Pitfalls. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
UI-71923
What
Adds a debugging hint to the
uipath-rpaskill for a UI-automation failure mode that a coding agent could not diagnose on its own.Symptom: an interaction faults with
UI element is invalideven though the selector still resolves, and neither increasing the delay nor changing the input mode helps.Cause: the interaction itself remounts the target as a new DOM node (e.g.
TypeInto's built-in click-before-typing, or a click that expands a dropdown/popup). The activity resolved the old node; the next action hits the now-detached one. It is a re-resolution problem, not timing.Fix: split the interactions into separate activities (e.g.
ClickthenTypeInto) so the second re-resolves its target against the new node.Changes
references/uia-elements-interaction-guide.md— new section "Debugging a failed interaction with an element" (generic heading; covers the remount mechanism, the diagnostic tell, and the fix).references/ui-automation-guide.md— one-line pointer to that section from Common UIA Pitfalls (keeps the pitfall list terse and routes the agent to the fuller guide).🤖 Generated with Claude Code