puppeteer/website/versioned_docs/version-21.5.2/api/puppeteer.frame.click.md
release-please[bot] a6b508aa36
chore: release main (#11364)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
2023-11-15 10:48:54 +00:00

38 lines
1.1 KiB
Markdown

---
sidebar_label: Frame.click
---
# Frame.click() method
Clicks the first element found that matches `selector`.
#### Signature:
```typescript
class Frame {
click(selector: string, options?: Readonly<ClickOptions>): Promise<void>;
}
```
## Parameters
| Parameter | Type | Description |
| --------- | ----------------------------------------------------------- | -------------------------- |
| selector | string | The selector to query for. |
| options | Readonly&lt;[ClickOptions](./puppeteer.clickoptions.md)&gt; | _(Optional)_ |
**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:
```ts
const [response] = await Promise.all([
page.waitForNavigation(waitOptions),
frame.click(selector, clickOptions),
]);
```