For the complete documentation index, see llms.txt. This page is also available as Markdown.

Element states

Learn what Exists, Displayed, Visible, Enabled, and Clickable mean for Elements.

Check and Wait Test Steps often ask whether an Element is present, shown, or ready to use. These states mean different things. Pick the one that matches what you need to prove.

Presence and visibility

State
What it means

Exists

The Element is in the DOM.

Displayed

The Element is shown on the page.

Visible

The Element is shown within the current viewport.

Exists only cares that the Element is in the page structure. It can still be hidden.

Displayed means the Element is shown. An Element that is off-screen can still be Displayed. If a parent is hiding the Element, it is not Displayed.

Visible means the Element is shown inside what the browser can see right now. Use it when the journey depends on the Element being on screen, not only present or shown somewhere on the page.

If you need to prove…
Use

The Element is in the page

Exists

The Element is shown

Displayed

The Element is on screen in the current view

Visible

Interaction

State
What it means

Enabled

The Element can be used. It is not disabled.

Disabled

The Element is disabled.

Clickable

The Element is Displayed and Enabled, so it is ready to click.

Use Enabled when the control should accept input. Use Clickable when the next step is a click or tap and the Element should be both shown and usable.

Selection and focus

State
What it means

Selected

The Element is selected or checked, such as a checkbox or radio button.

Focused

The Element has keyboard focus.

Checks and waits

Each state has matching Check Test Steps, and the presence, visibility, and interaction states also have Wait Test Steps.

Pro tip: Touch already waits for the Element to become clickable and scrolls it into view before clicking. Add an explicit Wait when the Flow needs to pause on a state before the next step.

Last updated