Filip/playwright
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs: update selectors doc to be more like a guide (#5048)

Browse source
This commit is contained in:
Pavel Feldman 2021-01-18 20:59:16 -08:00 committed by GitHub
parent 9caa8e80d7
commit 9e3bd78649
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 277 additions and 346 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

623
docs/src/selectors.md
View file

@ -3,142 +3,292 @@ id: selectors
title: "Element selectors" title: "Element selectors"
--- ---
Selectors query elements on the web page for interactions, like [`method: Page.click`], and to obtain `ElementHandle` through [`method: Page.$`]. Built-in selectors auto-pierce [shadow DOM](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM). Selectors are strings that point to the elements in the page. They are used to perform actions on those
elements by means of methods such as [`method: Page.click`], [`method: Page.fill`] and alike. All those
methods accept [`param: selector`] as their first argument.
<!-- TOC --> <!-- TOC -->
## Working with selectors ## Basic text selectors
Selector describes an element in the page. It can be used to obtain `ElementHandle` (see [`method: Page.$`] for example) or shortcut element operations to avoid intermediate handle (see [`method: Page.click`] for example). Text selectors locate elements that contain text nodes with the passed text.
Selector has the following format: `engine=body [>> engine=body]*`. Here `engine` is one of the supported [selector engines](./selectors.md) (e.g. `css` or `xpath`), and `body` is a selector body in the format of the particular engine. When multiple `engine=body` clauses are present (separated by `>>`), next one is queried relative to the previous one's result.
Playwright supports various selector engines:
* [Text] selectors, for example `text="Log in"`
* [CSS] selectors, including the following extensions:
- [Shadow piercing](#shadow-piercing) by default and [`:light`](#css-extension-light) pseudo-class
- [`:visible`](#css-extension-visible) pseudo-class
- [`:text`](#css-extension-text) pseudo-class
- [`:has`](#css-extension-has) and [`:is`](#css-extension-is) pseudo-classes
- [Position selectors](#css-extension-position), for example `button:right-of(article)`
* [XPath] selectors, for example `xpath=//html/body/div`
* [id selectors][id], for example `id=sign-in`
* [Custom selector engines](./extensibility.md)
For convenience, selectors in the wrong format are heuristically converted to the right format:
- selector starting with `//` or `..` is assumed to be `xpath=selector`;
- selector starting and ending with a quote (either `"` or `'`) is assumed to be `text=selector`;
- otherwise selector is assumed to be `css=selector`.
```js ```js
// queries 'div' css selector await page.click('text=Log in');
const handle = await page.$('css=div');
// queries '//html/body/div' xpath selector
const handle = await page.$('xpath=//html/body/div');
// queries '"foo"' text selector
const handle = await page.$('text="foo"');
// queries 'span' css selector inside the result of '//html/body/div' xpath selector
const handle = await page.$('xpath=//html/body/div >> css=span');
// converted to 'css=div'
const handle = await page.$('div');
// converted to 'xpath=//html/body/div'
const handle = await page.$('//html/body/div');
// converted to 'text="foo"'
const handle = await page.$('"foo"');
// queries '../span' xpath selector starting with the result of 'div' css selector
const handle = await page.$('div >> ../span');
// queries 'span' css selector inside the div handle
const handle = await divHandle.$('css=span');
``` ```
```python async ```python async
# queries 'div' css selector await page.click("text=Log in")
handle = await page.query_selector('css=div')
# queries '//html/body/div' xpath selector
handle = await page.query_selector('xpath=//html/body/div')
# queries '"foo"' text selector
handle = await page.query_selector('text="foo"')
# queries 'span' css selector inside the result of '//html/body/div' xpath selector
handle = await page.query_selector('xpath=//html/body/div >> css=span')
# converted to 'css=div'
handle = await page.query_selector('div')
# converted to 'xpath=//html/body/div'
handle = await page.query_selector('//html/body/div')
# converted to 'text="foo"'
handle = await page.query_selector('"foo"')
# queries '../span' xpath selector starting with the result of 'div' css selector
handle = await page.query_selector('div >> ../span')
# queries 'span' css selector inside the div handle
handle = await div_handle.query_selector('css=span')
``` ```
```python sync ```python sync
# queries 'div' css selector page.click("text=Log in")
handle = page.query_selector('css=div')
# queries '//html/body/div' xpath selector
handle = page.query_selector('xpath=//html/body/div')
# queries '"foo"' text selector
handle = page.query_selector('text="foo"')
# queries 'span' css selector inside the result of '//html/body/div' xpath selector
handle = page.query_selector('xpath=//html/body/div >> css=span')
# converted to 'css=div'
handle = page.query_selector('div')
# converted to 'xpath=//html/body/div'
handle = page.query_selector('//html/body/div')
# converted to 'text="foo"'
handle = page.query_selector('"foo"')
# queries '../span' xpath selector starting with the result of 'div' css selector
handle = page.query_selector('div >> ../span')
# queries 'span' css selector inside the div handle
handle = div_handle.query_selector('css=span')
``` ```
## Syntax By default, the match is case-insensitive, it ignores leading/trailing whitespace and searches for
Selectors are defined by selector engine name and selector body, `engine=body`. a substring. This means `text= Login` matches `<button>Button loGIN (click me)</button>`.
* `engine` refers to one of the supported engines Text body can be escaped with single or double quotes for precise matching, insisting on exact match,
* Built-in selector engines: [css], [text], [xpath] and [id selectors][id] including specified whitespace and case. This means `text="Login "` will only match
* Learn more about [custom selector engines](./extensibility.md) `<button>Login </button>` with exactly one space after "Login". Quoted text follows the usual escaping
* `body` refers to the query string for the respective engine rules, e.g. use `\"` to escape double quote in a double-quoted string: `text="foo\"bar"`.
* For `text`, body is the text content
* For `css`, body is a [css selector](https://developer.mozilla.org/en/docs/Web/CSS/CSS_Selectors)
Body format is assumed to ignore leading and trailing white spaces, so that extra whitespace can be added for readability. Text body can also be a JavaScript-like regex wrapped in `/` symbols. This means `text=/^\\s*Login$/i`
will match `<button> loGIN</button>` with any number of spaces before "Login" and no spaces after.
### Short-forms Input elements of the type `button` and `submit` are rendered with their value as text, and text
For convenience, common selectors have short-forms: engine finds them. For example, `text=Login` matches `<input type=button value="Login">`.
- Selector starting with `//` or `..` is assumed to be `xpath=selector`
- Example: `'//html'` is converted to `'xpath=//html'`. Selector string starting and ending with a quote (either `"` or `'`) is assumed to be a text selector.
- Selector starting and ending with a quote (either `"` or `'`) is assumed to be `text=selector` For example, Playwright converts `'"Login"'` to `'text="Login"'` internally.
- Example: `'"foo"'` is converted to `'text="foo"'`.
- Otherwise, selector is assumed to be `css=selector` ## Basic CSS selectors
- Example: `'div'` is converted to `'css=div'`.
Playwright augments standard CSS selectors in two ways:
* `css` engine pierces open shadow DOM by default.
* Playwright adds a few custom pseudo-classes like `:visible`.
```js
await page.click('button');
```
```python async
await page.click("button")
```
```python sync
page.click("button")
```
## Selecting visible elements
The `:visible` pseudo-class in CSS selectors matches the elements that are
[visible](./actionability.md#visible). For example, `input` matches all the inputs on the page, while
`input:visible` matches only visible inputs. This is useful to distinguish elements that are very
similar but differ in visibility.
:::note
It's usually better to follow the [best practices](#best-practices) and find a more reliable way to
uniquely identify the element.
:::
Consider a page with two buttons, first invisible and second visible.
```html
<button style='display: none'>Invisible</button>
<button>Visible</button>
```
* This will find the first button, because it is the first one in DOM order. Then it will wait for the button to become visible before clicking, or timeout while waiting:
```js
await page.click('button');
```
```python async
await page.click("button")
```
```python sync
page.click("button")
```
* This will find a second button, because it is visible, and then click it.
```js
await page.click('button:visible');
```
```python async
await page.click("button:visible")
```
```python sync
page.click("button:visible")
```
Use `:visible` with caution, because it has two major drawbacks:
* When elements change their visibility dynamically, `:visible` will give unpredictable results based on the timing.
* `:visible` forces a layout and may lead to querying being slow, especially when used with `page.waitForSelector(selector[, options])` method.
## Selecting elements that contain other elements
The `:has()` pseudo-class is an [experimental CSS pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:has). It returns an element if any of the selectors passed as parameters
relative to the :scope of the given element match at least one element.
Following snippet returns text content of an `<article>` element that has a `<div class=promo>` inside.
```js
await page.textContent('article:has(div.promo)');
```
```python async
await page.textContent("article:has(div.promo)")
```
```python sync
page.textContent("article:has(div.promo)")
```
## Selecting elements matching one of the conditions
The `:is()` pseudo-class is an [experimental CSS pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:is).
It is a function that takes a selector list as its argument, and selects any element that
can be selected by one of the selectors in that list. This is useful for writing large
selectors in a more compact form.
```js
// Clicks a <button> that has either a "Log in" or "Sign in" text.
await page.click('button:is(:text("Log in"), :text("Sign in"))');
```
```python async
# Clicks a <button> that has either a "Log in" or "Sign in" text.
await page.click('button:is(:text("Log in"), :text("Sign in"))')
```
```python sync
# Clicks a <button> that has either a "Log in" or "Sign in" text.
page.click('button:is(:text("Log in"), :text("Sign in"))')
```
## Selecting elements by text
The `:text` pseudo-class matches elements that have a text node child with specific text.
It is similar to the [text] engine, but can be used in combination with other `css` selector extensions.
There are a few variations that support different arguments:
* `:text("substring")` - Matches when element's text contains "substring" somewhere. Matching is case-insensitive. Matching also normalizes whitespace, for example it turns multiple spaces into one, trusn line breaks into spaces and ignores leading and trailing whitespace.
* `:text-is("string")` - Matches when element's text equals the "string". Matching is case-insensitive and normalizes whitespace.
* `button:text("Sign in")` - Text selector may be combined with regular CSS.
* `:text-matches("[+-]?\\d+")` - Matches text against a regular expression. Note that special characters like back-slash `\`, quotes `"`, square brackets `[]` and more should be escaped. Learn more about [regular expressions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp).
* `:text-matches("value", "i")` - Matches text against a regular expression with specified flags.
Click a button with text "Sign in":
```js
await page.click('button:text("Sign in")');
```
```python async
await page.click('button:text("Sign in")')
```
```python sync
page.click('button:text("Sign in")')
```
## Selecting elements in Shadow DOM
Our `css` and `text` engines pierce the [Shadow DOM](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM) by default:
- First it searches for the elements in the light DOM in the iteration order, and
- Then it searches recursively inside open shadow roots in the iteration order.
In particular, in `css` engines, any [Descendant combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Descendant_combinator)
or [Child combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Child_combinator) pierces an
arbitrary number of open shadow roots, including the implicit descendant combinator at the start of the
selector. It does not search inside closed shadow roots or iframes.
If you'd like to opt-out of this behavior, you can use `:light` CSS extension or `text:light` selector engine. They do not pierce shadow roots.
```js
await page.click(':light(.article > .header)');
```
```python async
await page.click(":light(.article > .header)")
```
```python sync
page.click(":light(.article > .header)")
```
More advanced Shadow DOM use cases:
```html
<article>
<div>In the light dom</div>
<div slot='myslot'>In the light dom, but goes into the shadow slot</div>
#shadow-root
<div class='in-the-shadow'>
<span class='content'>
In the shadow dom
#shadow-root
<li id='target'>Deep in the shadow</li>
</span>
</div>
<slot name='myslot'></slot>
</article>
```
- Both `"css=article div"` and `"css:light=article div"` match the first `<div>In the light dom</div>`.
- Both `"css=article > div"` and `"css:light=article > div"` match two `div` elements that are direct children of the `article`.
- `"css=article .in-the-shadow"` matches the `<div class='in-the-shadow'>`, piercing the shadow root, while `"css:light=article .in-the-shadow"` does not match anything.
- `"css:light=article div > span"` does not match anything, because both light-dom `div` elements do not contain a `span`.
- `"css=article div > span"` matches the `<span class='content'>`, piercing the shadow root.
- `"css=article > .in-the-shadow"` does not match anything, because `<div class='in-the-shadow'>` is not a direct child of `article`
- `"css:light=article > .in-the-shadow"` does not match anything.
- `"css=article li#target"` matches the `<li id='target'>Deep in the shadow</li>`, piercing two shadow roots.
## Selecting elements based on layout
Playwright can select elements based on the page layout. These can be combined with regular CSS for
better results, for example `input:right-of(:text("Password"))` matches an input field that is to the
right of text "Password".
:::note
Layout selectors depend on the page layout and may produce unexpected results. For example, a different
element could be matched when layout changes by one pixel.
:::
Layout selectors use [bounding client rect](https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect)
to compute distance and relative position of the elements.
* `:right-of(inner > selector)` - Matches elements that are to the right of any element matching the inner selector.
* `:left-of(inner > selector)` - Matches elements that are to the left of any element matching the inner selector.
* `:above(inner > selector)` - Matches elements that are above any of the elements matching the inner selector.
* `:below(inner > selector)` - Matches elements that are below any of the elements matching the inner selector.
* `:near(inner > selector)` - Matches elements that are near (within 50 CSS pixels) any of the elements matching the inner selector.
```js
// Fill an input to the right of "Username".
await page.fill('input:right-of(:text("Username"))');
// Click a button near the promo card.
await page.click('button:near(.promo-card)');
```
```python async
# Fill an input to the right of "Username".
await page.fill('input:right-of(:text("Username"))')
# Click a button near the promo card.
await page.click('button:near(.promo-card)')
```
```python sync
# Fill an input to the right of "Username".
page.fill('input:right-of(:text("Username"))')
# Click a button near the promo card.
page.click('button:near(.promo-card)')
```
## XPpath selectors
XPath engine is equivalent to [`Document.evaluate`](https://developer.mozilla.org/en/docs/Web/API/Document/evaluate).
Example: `xpath=//html/body`.
Malformed selector starting with `//` or `..` is assumed to be an xpath selector. For example, Playwright
converts `'//html/body'` to `'xpath=//html/body'`.
:::note
`xpath` does not pierce shadow roots
:::
## id, data-testid, data-test-id, data-test selectors
Attribute engines are selecting based on the corresponding attribute value. For example: `data-test-id=foo` is equivalent to `css=[data-test-id="foo"]`, and `id:light=foo` is equivalent to `css:light=[id="foo"]`.
## Chaining selectors
### Chaining selectors
Selectors defined as `engine=body` or in short-form can be combined with the `>>` token, e.g. `selector1 >> selector2 >> selectors3`. When selectors are chained, next one is queried relative to the previous one's result. Selectors defined as `engine=body` or in short-form can be combined with the `>>` token, e.g. `selector1 >> selector2 >> selectors3`. When selectors are chained, next one is queried relative to the previous one's result.
For example, For example,
@ -156,11 +306,13 @@ document
If a selector needs to include `>>` in the body, it should be escaped inside a string to not be confused with chaining separator, e.g. `text="some >> text"`. If a selector needs to include `>>` in the body, it should be escaped inside a string to not be confused with chaining separator, e.g. `text="some >> text"`.
### Intermediate matches ### Intermediate matches
By default, chained selectors resolve to an element queried by the last selector. A selector can be prefixed with `*` to capture elements that are queried by an intermediate selector. By default, chained selectors resolve to an element queried by the last selector. A selector can be prefixed with `*` to capture elements that are queried by an intermediate selector.
For example, `css=article >> text=Hello` captures the element with the text `Hello`, and `*css=article >> text=Hello` (note the `*`) captures the `article` element that contains some element with the text `Hello`. For example, `css=article >> text=Hello` captures the element with the text `Hello`, and `*css=article >> text=Hello` (note the `*`) captures the `article` element that contains some element with the text `Hello`.
## Best practices ## Best practices
The choice of selectors determines the resiliency of automation scripts. To reduce the maintenance burden, we recommend prioritizing user-facing attributes and explicit contracts. The choice of selectors determines the resiliency of automation scripts. To reduce the maintenance burden, we recommend prioritizing user-facing attributes and explicit contracts.
### Prioritize user-facing attributes ### Prioritize user-facing attributes
@ -255,7 +407,9 @@ page.click('data-test-id=directions')
``` ```
### Avoid selectors tied to implementation ### Avoid selectors tied to implementation
[xpath] and [css] can be tied to the DOM structure or implementation. These selectors can break when the DOM structure changes.
[xpath] and [css] can be tied to the DOM structure or implementation. These selectors can break when
the DOM structure changes.
```js ```js
// avoid long css or xpath chains // avoid long css or xpath chains
@ -275,230 +429,7 @@ page.click('#tsf > div:nth-child(2) > div.A8SBwf > div.RNNXgb > div > div.a4bIc
page.click('//*[@id="tsf"]/div[2]/div[1]/div[1]/div/div[2]/input') page.click('//*[@id="tsf"]/div[2]/div[1]/div[1]/div/div[2]/input')
``` ```
## CSS selector engine [text]: #basic-text-selectors
[css]: #basic-css-selectors
`css` is a default engine - any malformed selector not starting with `//` nor starting and ending with a quote is assumed to be a css selector. For example, Playwright converts `'span > button'` to `'css=span > button'`. [xpath]: #xpath-selectors
[id]: #id-data-testid-data-test-id-data-test-selectors
Playwright augments standard CSS selectors in two ways, see below for more details:
* `css` engine pierces open shadow DOM by default.
* Playwright adds a few custom pseudo-classes like `:visible`.
### Shadow piercing
`css:light` engine is equivalent to [`Document.querySelector`](https://developer.mozilla.org/en/docs/Web/API/Document/querySelector) and behaves according to the CSS spec. However, it does not pierce shadow roots, which may be inconvenient when working with [Shadow DOM and Web Components](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM). For that reason, `css` engine pierces shadow roots. More specifically, any [Descendant combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Descendant_combinator) or [Child combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Child_combinator) pierces an arbitrary number of open shadow roots, including the implicit descendant combinator at the start of the selector.
`css` engine first searches for elements in the light dom in the iteration order, and then recursively inside open shadow roots in the iteration order. It does not search inside closed shadow roots or iframes.
```html
<article>
<div>In the light dom</div>
<div slot='myslot'>In the light dom, but goes into the shadow slot</div>
<open mode shadow root>
<div class='in-the-shadow'>
<span class='content'>
In the shadow dom
<open mode shadow root>
<li id='target'>Deep in the shadow</li>
</open mode shadow root>
</span>
</div>
<slot name='myslot'></slot>
</open mode shadow root>
</article>
```
Note that `<open mode shadow root>` is not an html element, but rather a shadow root created with `element.attachShadow({mode: 'open'})`.
- Both `"css=article div"` and `"css:light=article div"` match the first `<div>In the light dom</div>`.
- Both `"css=article > div"` and `"css:light=article > div"` match two `div` elements that are direct children of the `article`.
- `"css=article .in-the-shadow"` matches the `<div class='in-the-shadow'>`, piercing the shadow root, while `"css:light=article .in-the-shadow"` does not match anything.
- `"css:light=article div > span"` does not match anything, because both light-dom `div` elements do not contain a `span`.
- `"css=article div > span"` matches the `<span class='content'>`, piercing the shadow root.
- `"css=article > .in-the-shadow"` does not match anything, because `<div class='in-the-shadow'>` is not a direct child of `article`
- `"css:light=article > .in-the-shadow"` does not match anything.
- `"css=article li#target"` matches the `<li id='target'>Deep in the shadow</li>`, piercing two shadow roots.
### CSS extension: visible
The `:visible` pseudo-class matches elements that are visible as defined in the [actionability](./actionability.md#visible) guide. For example, `input` matches all the inputs on the page, while `input:visible` matches only visible inputs. This is useful to distinguish elements that are very similar but differ in visibility, however it's usually better to follow [best practices](#best-practices) and find another way to select the element.
Consider a page with two buttons, first invisible and second visible.
```html
<button style='display: none'>Invisible</button>
<button>Visible</button>
```
* This will find the first button, because it is the first one in DOM order. Then it will wait for the button to become visible before clicking, or timeout while waiting:
```js
await page.click('button');
```
```python async
await page.click("button")
```
```python sync
page.click("button")
```
* This will find a second button, because it is visible, and then click it.
```js
await page.click('button:visible');
```
```python async
await page.click("button:visible")
```
```python sync
page.click("button:visible")
```
Use `:visible` with caution, because it has two major drawbacks:
* When elements change their visibility dynamically, `:visible` will give upredictable results based on the timing.
* `:visible` forces a layout and may lead to querying being slow, especially when used with `page.waitForSelector(selector[, options])` method.
### CSS extension: text
The `:text` pseudo-class matches elements that have a text node child with specific text. It is similar to the [text] engine. There are a few variations that support different arguments:
* `:text("substring")` - Matches when element's text contains "substring" somewhere. Matching is case-insensitive. Matching also normalizes whitespace, for example it turns multiple spaces into one, trusn line breaks into spaces and ignores leading and trailing whitespace.
* `:text-is("string")` - Matches when element's text equals the "string". Matching is case-insensitive and normalizes whitespace.
* `button:text("Sign in")` - Text selector may be combined with regular CSS.
* `:text-matches("[+-]?\\d+")` - Matches text against a regular expression. Note that special characters like back-slash `\`, quotes `"`, square brackets `[]` and more should be escaped. Learn more about [regular expressions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp).
* `:text-matches("value", "i")` - Matches text against a regular expression with specified flags.
```js
// Click a button with text "Sign in".
await page.click('button:text("Sign in")');
```
```python async
# Click a button with text "Sign in".
await page.click('button:text("Sign in")')
```
```python sync
# Click a button with text "Sign in".
page.click('button:text("Sign in")')
```
### CSS extension: has
The `:has()` pseudo-class is an [experimental CSS pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:has) that is supported by Playwright.
```js
// Returns text content of an <article> element that has a <div class=promo> inside.
await page.textContent('article:has(div.promo)');
```
```python async
# Returns text content of an <article> element that has a <div class=promo> inside.
await page.textContent("article:has(div.promo)")
```
```python sync
# Returns text content of an <article> element that has a <div class=promo> inside.
page.textContent("article:has(div.promo)")
```
### CSS extension: is
The `:is()` pseudo-class is an [experimental CSS pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:is) that is supported by Playwright.
```js
// Clicks a <button> that has either a "Log in" or "Sign in" text.
await page.click('button:is(:text("Log in"), :text("Sign in"))');
```
```python async
# Clicks a <button> that has either a "Log in" or "Sign in" text.
await page.click('button:is(:text("Log in"), :text("Sign in"))')
```
```python sync
# Clicks a <button> that has either a "Log in" or "Sign in" text.
page.click('button:is(:text("Log in"), :text("Sign in"))')
```
### CSS extension: light
`css` engine [pierces shadow](#shadow-piercing) by default. It is possible to disable this behavior by wrapping a selector in `:light` pseudo-class: `:light(section > button.class)` matches in light DOM only.
```js
await page.click(':light(.article > .header)');
```
```python async
await page.click(":light(.article > .header)")
```
```python sync
page.click(":light(.article > .header)")
```
### CSS extension: position
Playwright provides position selectors based on the page layout. These can be combined with regular CSS for better results, for example `input:right-of(:text("Password"))` matches an input field that is to the right of text "Password".
Note that position selectors depend on the page layout and may produce unexpected results. For example, a different element could be matched when layout changes by one pixel.
Position selectors use [bounding client rect](https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect) to compute distance and relative position of the elements.
* `:right-of(inner > selector)` - Matches elements that are to the right of any element matching the inner selector.
* `:left-of(inner > selector)` - Matches elements that are to the left of any element matching the inner selector.
* `:above(inner > selector)` - Matches elements that are above any of the elements matching the inner selector.
* `:below(inner > selector)` - Matches elements that are below any of the elements matching the inner selector.
* `:near(inner > selector)` - Matches elements that are near (within 50 CSS pixels) any of the elements matching the inner selector.
```js
// Fill an input to the right of "Username".
await page.fill('input:right-of(:text("Username"))');
// Click a button near the promo card.
await page.click('button:near(.promo-card)');
```
```python async
# Fill an input to the right of "Username".
await page.fill('input:right-of(:text("Username"))')
# Click a button near the promo card.
await page.click('button:near(.promo-card)')
```
```python sync
# Fill an input to the right of "Username".
page.fill('input:right-of(:text("Username"))')
# Click a button near the promo card.
page.click('button:near(.promo-card)')
```
## Xpath selector engine
XPath engine is equivalent to [`Document.evaluate`](https://developer.mozilla.org/en/docs/Web/API/Document/evaluate). Example: `xpath=//html/body`.
Malformed selector starting with `//` or `..` is assumed to be an xpath selector. For example, Playwright converts `'//html/body'` to `'xpath=//html/body'`.
Note that `xpath` does not pierce shadow roots.
## Text selector engine
Text engine finds an element that contains a text node with the passed text. For example, `page.click('text=Login')` clicks on a login button, and `page.waitForSelector('"lazy loaded text")` waits for the `"lazy loaded text"` to appear in the page.
- By default, the match is case-insensitive, ignores leading/trailing whitespace and searches for a substring. This means `text= Login` matches `<button>Button loGIN (click me)</button>`.
- Text body can be escaped with single or double quotes for precise matching, insisting on exact match, including specified whitespace and case. This means `text="Login "` will only match `<button>Login </button>` with exactly one space after "Login". Quoted text follows the usual escaping rules, e.g. use `\"` to escape double quote in a double-quoted string: `text="foo\"bar"`.
- Text body can also be a JavaScript-like regex wrapped in `/` symbols. This means `text=/^\\s*Login$/i` will match `<button> loGIN</button>` with any number of spaces before "Login" and no spaces after.
- Input elements of the type `button` and `submit` are rendered with their value as text, and text engine finds them. For example, `text=Login` matches `<input type=button value="Login">`.
Malformed selector starting and ending with a quote (either `"` or `'`) is assumed to be a text selector. For example, Playwright converts `page.click('"Login"')` to `page.click('text="Login"')`.
`text` engine open pierces shadow roots similarly to `css`, while `text:light` does not. Text engine first searches for elements in the light dom in the iteration order, and then recursively inside open shadow roots in the iteration order. It does not search inside closed shadow roots or iframes.
### id, data-testid, data-test-id, data-test selector engines
Attribute engines are selecting based on the corresponding attribute value. For example: `data-test-id=foo` is equivalent to `css=[data-test-id="foo"]`, and `id:light=foo` is equivalent to `css:light=[id="foo"]`.
[css]: #css-selector-engine
[text]: #text-selector-engine
[xpath]: #xpath-selector-engine
[id]: #id-data-testid-data-test-id-data-test-selector-engines