Playwright performs a range of actionability checks on the elements before making actions to ensure these actions behave as expected. It auto-waits for all the relevant checks to pass and only then performs the requested action. If the required checks do not pass within the given
timeout, action fails with the
For example, for Page.ClickAsync(), Playwright will ensure that:
- element is Attached to the DOM
- element is Visible
- element is Stable, as in not animating or completed animation
- element Receives Events, as in not obscured by other elements
- element is Enabled
Here is the complete list of actionability checks performed for each action:
Some actions like Page.ClickAsync() support
force option that disables non-essential actionability checks, for example passing truthy
force to Page.ClickAsync() method will not check that the target element actually receives click events.
You can check the actionability state of the element using one of the following methods as well. This is typically not necessary, but it helps writing assertive tests that ensure that after certain actions, elements reach actionable state:
Element is considered attached when it is connected to a Document or a ShadowRoot.
Element is considered visible when it has non-empty bounding box and does not have
visibility:hidden computed style. Note that elements of zero size or with
display:none are not considered visible.
Element is considered stable when it has maintained the same bounding box for at least two consecutive animation frames.
Element is considered enabled unless it is a
<textarea> with a
Element is considered editable when it is enabled and does not have
readonly property set.
Element is considered receiving pointer events when it is the hit target of the pointer event at the action point. For example, when clicking at the point
(10;10), Playwright checks whether some other element (usually an overlay) will instead capture the click at
For example, consider a scenario where Playwright will click
Sign Up button regardless of when the Page.ClickAsync() call was made:
- page is checking that user name is unique and
Sign Upbutton is disabled;
- after checking with the server, the disabled
Sign Upbutton is replaced with another one that is now enabled.