8054bac046
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
45 lines
1.3 KiB
Markdown
45 lines
1.3 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?: {
|
|
delay?: number;
|
|
button?: MouseButton;
|
|
clickCount?: number;
|
|
}
|
|
): Promise<void>;
|
|
}
|
|
```
|
|
|
|
## Parameters
|
|
|
|
| Parameter | Type | Description |
|
|
| --------- | -------------------------------------------------------------------------------------------- | -------------------------- |
|
|
| selector | string | The selector to query for. |
|
|
| options | { delay?: number; button?: [MouseButton](./puppeteer.mousebutton.md); clickCount?: number; } | <i>(Optional)</i> |
|
|
|
|
**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),
|
|
]);
|
|
```
|