puppeteer/docs/api/puppeteer.frame.click.md

73 lines
1.0 KiB
Markdown
Raw Normal View History

2022-07-05 13:41:43 +00:00
---
sidebar_label: Frame.click
---
# Frame.click() method
Clicks the first element found that matches `selector`.
2022-07-05 13:41:43 +00:00
#### Signature:
2022-07-05 13:41:43 +00:00
```typescript
class Frame {
2023-04-25 11:28:47 +00:00
click(selector: string, options?: Readonly<ClickOptions>): Promise<void>;
2022-07-05 13:41:43 +00:00
}
```
## Parameters
<table><thead><tr><th>
2022-07-05 13:41:43 +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&lt;[ClickOptions](./puppeteer.clickoptions.md)&gt;
</td><td>
_(Optional)_
</td></tr>
</tbody></table>
2022-07-05 13:41:43 +00:00
**Returns:**
Promise&lt;void&gt;
## 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:
2022-07-05 13:41:43 +00:00
```ts
2022-07-05 13:41:43 +00:00
const [response] = await Promise.all([
page.waitForNavigation(waitOptions),
frame.click(selector, clickOptions),
]);
```