3aee641c3d
🤖 I have created a release *beep* *boop* --- ## [18.1.0](https://github.com/puppeteer/puppeteer/compare/v18.0.5...v18.1.0) (2022-10-05) ### Features * **chromium:** roll to Chromium 107.0.5296.0 (r1045629) ([#9039](https://github.com/puppeteer/puppeteer/issues/9039)) ([022fbde](022fbde85e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
1.3 KiB
1.3 KiB
| sidebar_label |
|---|
| Frame.click |
Frame.click() method
Clicks the first element found that matches selector.
Signature:
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; clickCount?: number; } | (Optional) |
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:
const [response] = await Promise.all([
page.waitForNavigation(waitOptions),
frame.click(selector, clickOptions),
]);