Locators and waits

Choose a stable locator for the intended target. The selected Robot controls which types and options it can execute.

Locator types

Type	Use and targets
CSS	Structured element selection in Browser and HTML.
XPath	Browser element paths, including supported relative queries.
Text	Browser literal text matching, case-sensitive with whitespace normalization.
JavaScript	Browser element selection using an authored expression; no automatic native picking equivalent.
Coordinates	Browser or Desktop numeric display points; Browser additionally supports explicit axis expressions.

Text selects deepest matching elements; an exact-looking label may still have duplicates. Prefer stable attributes and review measured match counts rather than relying on the first broad button selector.

Inspect and adopt

Select CSS, Text or XPath in the field before inspecting. The picker proposes the selected type, not a CSS substitute for XPath/Text. Review ranked alternatives and adopt one deliberately. Its field remains a pending edit until Apply action.

A preview shows the current matches and can highlight a parent family and relative child targets. A chosen index selects one match; counts can describe the wider selection. Partial/sample indicators matter. Inspection does not execute a click or prove future uniqueness.

Selection and visibility

Reverse/range/index options change which matches are selected; indexes are zero-based within the ordered range. An explicit visibility filter excludes elements that do not meet its current viewport/style/center-coverage test. It is not a guarantee of general clickability. Without the filter, presence can include hidden or offscreen elements.

HTML has no rendered-layout visibility test. Some stored options may be refused rather than silently ignored; retain them for explicit repair.

Relative scope

Use inherited context for children inside the current row. Empty inherited CSS selects that row/root. An absolute locator searches from the document instead. Relative XPath such as .//td keeps a row-relative intention.

Locator ancestry and context.parent differ: the latter follows nested action execution. A temporary Parent row inspection choice does not change the authored Container or create an active record assembly.

Coordinate picking and expressions

Choose Pick coordinates from display, then click/tap the intended point. That gesture selects a local point without sending the actual action click. Escape cancels it. Apply the edited action to retain the new numbers.

Browser points use the full visible Browser display origin, including its bars, while actions must still target the supported page region. Desktop points use its full desktop, including decorations/panels. Both remain absolute inside collections.

Browser axes offer Number or Expression. For example ${200 + Math.random() * 50} is an explicit coordinate expression evaluated when the action runs. It must produce a valid number; the resulting position truncates toward zero. It is a separate coordinate capability, not a way to add arithmetic to ordinary variable templates. Desktop supports numeric axes only. Picking replaces expressions with the deliberately selected numeric point.

Waits

Navigation completion does not establish dynamic application readiness. Wait for the element the next action needs. Element waits support existence/absence; duration is in milliseconds. Zero performs one element check.

Wait also supports a variable duration or an inclusive Random minimum/maximum. Reversed ranges fail; equal endpoints including zero are valid. On HTML, a wait does not refetch or execute scripts to update downloaded source.

The shared action timeout concerns initial locator appearance, not a deadline for all action work. Omission preserves ordinary behavior; explicit zero retains the compatibility fallback of 3000 milliseconds. It is separate from Wait’s own duration.