This method fetches an element with selector, scrolls it into view if needed, and then uses Page.mouse to click in the center of the element. If there’s no element matching selector, the method throws an error.
class Page {
click(selector: string, options?: Readonly<ClickOptions>): Promise<void>;
}
| Parameter | Type | Description |
|---|---|---|
| selector | string | [selector](https://pptr.dev/guides/page-interactions#selectors) to query the page for. [CSS selectors](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors) can be passed as-is and a [Puppeteer-specific selector syntax](https://pptr.dev/guides/page-interactions#non-css-selectors) allows querying by [text](https://pptr.dev/guides/page-interactions#text-selectors--p-text), [a11y role and name](https://pptr.dev/guides/page-interactions#aria-selectors--p-aria), and [xpath](https://pptr.dev/guides/page-interactions#xpath-selectors--p-xpath) and [combining these queries across shadow roots](https://pptr.dev/guides/page-interactions#querying-elements-in-shadow-dom). Alternatively, you can specify the selector type using a [prefix](https://pptr.dev/guides/page-interactions#prefixed-selector-syntax). If there are multiple elements satisfying the `selector`, the first will be clicked |
| options | Readonly<[ClickOptions](./puppeteer.clickoptions.md)> | _(Optional)_ `Object` |
Returns:
Promise<void>
Promise which resolves when the element matching selector is successfully clicked. The Promise will be rejected if there is no element matching selector.
Bear in mind that 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),
page.click(selector, clickOptions),
]);
Shortcut for page.mainFrame().click(selector\[, options\]).