Page
Page provides methods to interact with a single tab in a Browser, or an extension background page in Chromium. One Browser instance might have multiple Page instances.
This example creates a page, navigates it to a URL, and then saves a screenshot:
import com.microsoft.playwright.*;
public class Example {
public static void main(String[] args) {
try (Playwright playwright = Playwright.create()) {
BrowserType webkit = playwright.webkit();
Browser browser = webkit.launch();
BrowserContext context = browser.newContext();
Page page = context.newPage();
page.navigate("https://example.com");
page.screenshot(new Page.ScreenshotOptions().setPath(Paths.get("screenshot.png")));
browser.close();
}
}
}
The Page class emits various events (described below) which can be handled using any of Node's native EventEmitter methods, such as on, once or removeListener.
This example logs a message for a single page load event:
page.onLoad(p -> System.out.println("Page loaded!"));
To unsubscribe from events use the removeListener method:
Consumer<Request> logRequest = interceptedRequest -> {
System.out.println("A request was made: " + interceptedRequest.url());
};
page.onRequest(logRequest);
// Sometime later...
page.offRequest(logRequest);
Methods
addInitScript
Added before v1.9Adds a script which would be evaluated in one of the following scenarios:
- Whenever the page is navigated.
- Whenever the child frame is attached or navigated. In this case, the script is evaluated in the context of the newly attached frame.
The script is evaluated after the document was created but before any of its scripts were run. This is useful to amend the JavaScript environment, e.g. to seed Math.random.
Usage
An example of overriding Math.random before the page loads:
// preload.js
Math.random = () => 42;
// In your playwright script, assuming the preload.js file is in same directory
page.addInitScript(Paths.get("./preload.js"));
The order of evaluation of multiple scripts installed via BrowserContext.addInitScript() and Page.addInitScript() is not defined.
Arguments
Returns
- [Disposable]#
addLocatorHandler
Added in: v1.42When testing a web page, sometimes unexpected overlays like a "Sign up" dialog appear and block actions you want to automate, e.g. clicking a button. These overlays don't always show up in the same way or at the same time, making them tricky to handle in automated tests.
This method lets you set up a special function, called a handler, that activates when it detects that overlay is visible. The handler's job is to remove the overlay, allowing your test to continue as if the overlay wasn't there.
Things to keep in mind:
- When an overlay is shown predictably, we recommend explicitly waiting for it in your test and dismissing it as a part of your normal test flow, instead of using Page.addLocatorHandler().
- Playwright checks for the overlay every time before executing or retrying an action that requires an actionability check, or before performing an auto-waiting assertion check. When overlay is visible, Playwright calls the handler first, and then proceeds with the action/assertion. Note that the handler is only called when you perform an action/assertion - if the overlay becomes visible but you don't perform any actions, the handler will not be triggered.
- After executing the handler, Playwright will ensure that overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with setNoWaitAfter.
- The execution time of the handler counts towards the timeout of the action/assertion that executed the handler. If your handler takes too long, it might cause timeouts.
- You can register multiple handlers. However, only a single handler will be running at a time. Make sure the actions within a handler don't depend on another handler.
Running the handler will alter your page state mid-test. For example it will change the currently focused element and move the mouse. Make sure that actions that run after the handler are self-contained and do not rely on the focus and mouse state being unchanged.
For example, consider a test that calls Locator.focus() followed by Keyboard.press(). If your handler clicks a button between these two actions, the focused element most likely will be wrong, and key press will happen on the unexpected element. Use Locator.press() instead to avoid this problem.
Another example is a series of mouse actions, where Mouse.move() is followed by Mouse.down(). Again, when the handler runs between these two actions, the mouse position will be wrong during the mouse down. Prefer self-contained actions like Locator.click() that do not rely on the state being unchanged by a handler.
Usage
An example that closes a "Sign up to the newsletter" dialog when it appears:
// Setup the handler.
page.addLocatorHandler(page.getByText("Sign up to the newsletter"), () -> {
page.getByRole(AriaRole.BUTTON, new Page.GetByRoleOptions().setName("No thanks")).click();
});
// Write the test as usual.
page.navigate("https://example.com");
page.getByRole("button", Page.GetByRoleOptions().setName("Start here")).click();
An example that skips the "Confirm your security details" page when it is shown:
// Setup the handler.
page.addLocatorHandler(page.getByText("Confirm your security details"), () -> {
page.getByRole(AriaRole.BUTTON, new Page.GetByRoleOptions().setName("Remind me later")).click();
});
// Write the test as usual.
page.navigate("https://example.com");
page.getByRole("button", Page.GetByRoleOptions().setName("Start here")).click();
An example with a custom callback on every actionability check. It uses a <body> locator that is always visible, so the handler is called before every actionability check. It is important to specify setNoWaitAfter, because the handler does not hide the <body> element.
// Setup the handler.
page.addLocatorHandler(page.locator("body"), () -> {
page.evaluate("window.removeObstructionsForTestIfNeeded()");
}, new Page.AddLocatorHandlerOptions().setNoWaitAfter(true));
// Write the test as usual.
page.navigate("https://example.com");
page.getByRole("button", Page.GetByRoleOptions().setName("Start here")).click();
Handler takes the original locator as an argument. You can also automatically remove the handler after a number of invocations by setting setTimes:
page.addLocatorHandler(page.getByLabel("Close"), locator -> {
locator.click();
}, new Page.AddLocatorHandlerOptions().setTimes(1));
Arguments
-
Locator that triggers the handler.
-
Function that should be run once locator appears. This function should get rid of the element that blocks actions like click.
-
optionsPage.AddLocatorHandlerOptions(optional)-
setNoWaitAfterboolean (optional) Added in: v1.44#By default, after calling the handler Playwright will wait until the overlay becomes hidden, and only then Playwright will continue with the action/assertion that triggered the handler. This option allows to opt-out of this behavior, so that overlay can stay visible after the handler has run.
-
setTimesint (optional) Added in: v1.44#Specifies the maximum number of times this handler should be called. Unlimited by default.
-
Returns
addScriptTag
Added before v1.9Adds a <script> tag into the page with the desired url or content. Returns the added tag when the script's onload fires or when the script content was injected into frame.
Usage
Page.addScriptTag();
Page.addScriptTag(options);
Arguments
optionsPage.AddScriptTagOptions(optional)-
Raw JavaScript content to be injected into frame.
-
Path to the JavaScript file to be injected into frame. If
pathis a relative path, then it is resolved relative to the current working directory. -
Script type. Use 'module' in order to load a JavaScript ES6 module. See script for more details.
-
URL of a script to be added.
-
Returns
addStyleTag
Added before v1.9Adds a <link rel="stylesheet"> tag into the page with the desired url or a <style type="text/css"> tag with the content. Returns the added tag when the stylesheet's onload fires or when the CSS content was injected into frame.
Usage
Page.addStyleTag();
Page.addStyleTag(options);
Arguments
optionsPage.AddStyleTagOptions(optional)
Returns
ariaSnapshot
Added in: v1.59Captures the aria snapshot of the page. Read more about aria snapshots.
Usage
Page.ariaSnapshot();
Page.ariaSnapshot(options);
Arguments
optionsPage.AriaSnapshotOptions(optional)-
setBoxesboolean (optional) Added in: v1.60#When
true, appends each element's bounding box as[box=x,y,width,height]to the snapshot. Coordinates are relative to the viewport, in CSS pixels, as returned byElement.getBoundingClientRect(). Defaults tofalse. -
When specified, limits the depth of the snapshot.
-
setModeenum AriaSnapshotMode { AI, DEFAULT }(optional)#When set to
"ai", returns a snapshot optimized for AI consumption: including element references like[ref=e2]and snapshots of<iframe>s. Defaults to"default". -
Maximum time in milliseconds. Defaults to
30000(30 seconds). Pass0to disable timeout. The default value can be changed by using the BrowserContext.setDefaultTimeout() or Page.setDefaultTimeout() methods.
-
Returns
bringToFront
Added before v1.9Brings page to front (activates tab).
Usage
Page.bringToFront();
Returns
cancelPickLocator
Added in: v1.59Cancels an ongoing Page.pickLocator() call by deactivating pick locator mode. If no pick locator mode is active, this method is a no-op.
Usage
Page.cancelPickLocator();
Returns
clearConsoleMessages
Added in: v1.59Clears all stored console messages from this page. Subsequent calls to Page.consoleMessages() will only return messages logged after the clear.
Usage
Page.clearConsoleMessages();
Returns
clearPageErrors
Added in: v1.59Clears all stored page errors from this page. Subsequent calls to Page.pageErrors() will only return errors thrown after the clear.
Usage
Page.clearPageErrors();
Returns
close
Added before v1.9If setRunBeforeUnload is false, does not run any unload handlers and waits for the page to be closed. If setRunBeforeUnload is true the method will run unload handlers, but will not wait for the page to close.
By default, page.close() does not run beforeunload handlers.
if setRunBeforeUnload is passed as true, a beforeunload dialog might be summoned and should be handled manually via Page.onDialog(handler) event.
Usage
Page.close();
Page.close(options);
Arguments
optionsPage.CloseOptions(optional)-
setReasonString (optional) Added in: v1.40#The reason to be reported to the operations interrupted by the page closure.
-
setRunBeforeUnloadboolean (optional)#Defaults to
false. Whether to run the before unload page handlers.
-
Returns
consoleMessages
Added in: v1.56Returns up to (currently) 200 last console messages from this page. See Page.onConsoleMessage(handler) for more details.
Usage
Page.consoleMessages();
Page.consoleMessages(options);
Arguments
optionsPage.ConsoleMessagesOptions(optional)-
setFilterenum ConsoleMessagesFilter { ALL, SINCE_NAVIGATION }(optional) Added in: v1.59#Controls which messages are returned:
-
Returns
content
Added before v1.9Gets the full HTML contents of the page, including the doctype.
Usage
Page.content();
Page.content(options);
Arguments
optionsPage.ContentOptions(optional)-
setIncludeShadowboolean (optional) Added in: v1.64#When true, contents of open shadow roots are included as declarative shadow DOM, i.e.
<template shadowrootmode="open">elements nested inside their host elements. Closed shadow roots are never included. Defaults tofalse.
-
Returns
context
Added before v1.9Get the browser context that the page belongs to.
Usage
Page.context();
Returns
dragAndDrop
Added in: v1.13This method drags the source element to the target element. It will first move to the source element, perform a mousedown, then move to the target element and perform a mouseup.
Usage
page.dragAndDrop("#source", "#target");
// or specify exact positions relative to the top-left corners of the elements:
page.dragAndDrop("#source", "#target", new Page.DragAndDropOptions()
.setSourcePosition(34, 7).setTargetPosition(10, 20));
Arguments
-
A selector to search for an element to drag. If there are multiple elements satisfying the selector, the first will be used.
-
A selector to search for an element to drop onto. If there are multiple elements satisfying the selector, the first will be used.
-
optionsPage.DragAndDropOptions(optional)-
Whether to bypass the actionability checks. Defaults to
false. -
setNoWaitAfterboolean (optional)#DeprecatedThis option has no effect.
This option has no effect.
-
setScrollenum ScrollMode { AUTO, NONE }(optional) Added in: v1.62#Controls whether Playwright scrolls the element into view before performing the action. Defaults to
"auto", which scrolls the element into view when necessary, including scrolling nested scrollable containers. When set to"none", Playwright does not scroll the element and the action fails if the element is not already in the viewport. This is useful to assert that an element is reachable by the user without additional scrolling. -
setSourcePositionSourcePosition (optional) Added in: v1.14#Clicks on the source element at this point relative to the top-left corner of the element's padding box. If not specified, some visible point of the element is used.
-
setStepsint (optional) Added in: v1.57#Defaults to 1. Sends
ninterpolatedmousemoveevents to represent travel between themousedownandmouseupof the drag. When set to 1, emits a singlemousemoveevent at the destination location. -
setStrictboolean (optional) Added in: v1.14#When true, the call requires selector to resolve to a single element. If given selector resolves to more than one element, the call throws an exception.
-
setTargetPositionTargetPosition (optional) Added in: v1.14#Drops on the target element at this point relative to the top-left corner of the element's padding box. If not specified, some visible point of the element is used.
-
Maximum time in milliseconds. Defaults to
30000(30 seconds). Pass0to disable timeout. The default value can be changed by using the BrowserContext.setDefaultTimeout() or Page.setDefaultTimeout() methods. -
When set, this method only performs the actionability checks and skips the action. Defaults to
false. Useful to wait until the element is ready for the action without performing it.
-
Returns