Point, Click, and Turn a Page Element into a Selector

Turn Visual Selection into Automated Commands

The element picker gives you a direct way to identify page elements without inspecting HTML. You activate the picker, move your cursor over the element you want to target, and RTILA X highlights the element with a visible outline. When you click, the picker generates a selector and inserts it into the current automation command.

This approach is much faster than manually reading class names or testing CSS rules. The picker understands the rendered page, including elements created by JavaScript frameworks, so it can often target components that are difficult to find through static source view.

How the Picker Works

The picker inspects the element under the cursor and builds a candidate selector. RTILA X ranks several possible selectors based on uniqueness and stability, then chooses a sensible default. You can see the generated selector in the command configuration panel and switch to a different candidate if the first choice looks fragile.

The picker can also capture multiple similar elements when you need a repeating pattern. You can activate grouping mode, select the first item in a list, and let RTILA X extend the selector to all matching items. This is especially useful for product grids, search results, and data tables.

Using the Picker Inside Recorded Steps

After recording a workflow, you can use the element picker to fix any step that was not captured exactly as you wanted. Instead of guessing which CSS rule the recorder used, you click the target directly and replace the old selector with the new one.

This workflow is ideal for teams that want to keep automation accessible to non-technical users. The person building the automation does not need to understand XPath syntax; they need to know which button or field to click. The picker translates that visual intention into a technical selector.

Picker Tips for Stable Workflows

Stable workflows depend on stable selectors. When you use the picker, prefer elements with visible text, unique IDs, or structural context over class names that change with every deployment. You can also combine the picker with wait commands so the automation targets the element only after it appears.

Because the picker is available in both the desktop app and the Chrome extension, you can create selectors wherever you are already browsing. That flexibility reduces the friction of building automation and makes visual selector creation feel like a natural part of the normal page exploration process.