2022-08-16 11:58:16 +00:00
---
sidebar_label: Frame.click
---
# Frame.click() method
Clicks the first element found that matches `selector` .
2022-10-24 14:31:12 +00:00
#### Signature:
2022-08-16 11:58:16 +00:00
```typescript
class Frame {
2023-04-25 14:59:34 +00:00
click(selector: string, options?: Readonly< ClickOptions > ): Promise< void > ;
2022-08-16 11:58:16 +00:00
}
```
## Parameters
2024-03-25 13:03:57 +00:00
< table > < thead > < tr > < th >
2022-08-16 11:58:16 +00:00
2024-03-25 13:03:57 +00:00
Parameter
< / th > < th >
Type
< / th > < th >
Description
< / th > < / tr > < / thead >
< tbody > < tr > < td >
selector
< / td > < td >
string
< / td > < td >
The selector to query for.
< / td > < / tr >
< tr > < td >
options
< / td > < td >
Readonly< [ClickOptions](./puppeteer.clickoptions.md)>
< / td > < td >
_(Optional)_
< / td > < / tr >
< / tbody > < / table >
2022-08-16 11:58:16 +00:00
**Returns:**
Promise< void>
## Remarks
If `click()` triggers a navigation event and there's a separate `page.waitForNavigation()` promise to be resolved, you may end up with a race condition that yields unexpected results. The correct pattern for click and wait for navigation is the following:
```ts
const [response] = await Promise.all([
page.waitForNavigation(waitOptions),
frame.click(selector, clickOptions),
]);
```