import LiteYouTube from '@site/src/components/LiteYouTube';

New [property: Page.screencast] API provides a unified interface for capturing page content with:

• Screencast recordings
• Action annotations
• Visual overlays
• Real-time frame capture
• Agentic video receipts

Screencast recording — record video with precise start/stop control, as an alternative to the [option: Browser.newContext.recordVideoDir] option:

page.screencast.start(path="video.webm")
# ... perform actions ...
page.screencast.stop()

Action annotations — enable built-in visual annotations that highlight interacted elements and display action titles during recording:

page.screencast.show_actions(position="top-right")

[method: Screencast.showActions] accepts position ('top-left', 'top', 'top-right', 'bottom-left', 'bottom', 'bottom-right'), duration (ms per annotation), and font_size (px). Returns a disposable to stop showing actions.

Visual overlays — add chapter titles and custom HTML overlays on top of the page for richer narration:

page.screencast.show_chapter("Adding TODOs",
    description="Type and press enter for each TODO",
    duration=1000,
)

page.screencast.show_overlay('<div style="color: red">Recording</div>')

Real-time frame capture — stream JPEG-encoded frames for custom processing like thumbnails, live previews, AI vision, and more:

page.screencast.start(
    on_frame=lambda frame: send_to_vision_model(frame["data"]),
)

Agentic video receipts — coding agents can produce video evidence of their work. After completing a task, an agent can record a walkthrough video with rich annotations for human review:

page.screencast.start(path="receipt.webm")
page.screencast.show_actions(position="top-right")

page.screencast.show_chapter("Verifying checkout flow",
    description="Added coupon code support per ticket #1234",
)

# Agent performs the verification steps...
page.locator("#coupon").fill("SAVE20")
page.locator("#apply-coupon").click()
expect(page.locator(".discount")).to_contain_text("20%")

page.screencast.show_chapter("Done",
    description="Coupon applied, discount reflected in total",
)

page.screencast.stop()

The resulting video serves as a receipt: chapter titles provide context, action annotations highlight each interaction, and the visual walkthrough is faster to review than text logs.

• Method [method: Page.ariaSnapshot] to capture the aria snapshot of the page — equivalent to page.locator('body').aria_snapshot().
• Options depth and mode in [method: Locator.ariaSnapshot].
• Method [method: Locator.normalize] converts a locator to follow best practices like test ids and aria roles.
• Method [method: Page.pickLocator] enters an interactive mode where hovering over elements highlights them and shows the corresponding locator. Click an element to get its [Locator] back. Use [method: Page.cancelPickLocator] to cancel.

• [property: Page.screencast] provides video recording, real-time frame streaming, and overlay management.
• Methods [method: Screencast.start] and [method: Screencast.stop] for recording and frame capture.
• Methods [method: Screencast.showActions] and [method: Screencast.hideActions] for action annotations.
• Methods [method: Screencast.showChapter] and [method: Screencast.showOverlay] for visual overlays.
• Methods [method: Screencast.showOverlays] and [method: Screencast.hideOverlays] for overlay visibility control.

• Method [method: BrowserContext.setStorageState] clears existing cookies, local storage, and IndexedDB for all origins and sets a new storage state — no need to create a new context.
• Methods [method: Page.clearConsoleMessages] and [method: Page.clearPageErrors] to clear stored messages and errors.
• Option filter in [method: Page.consoleMessages] and [method: Page.pageErrors] controls which messages are returned.
• Method [method: ConsoleMessage.timestamp].

• [property: BrowserContext.debugger] provides programmatic control over the Playwright debugger.
• Method [method: BrowserContext.isClosed].
• Method [method: Request.existingResponse] returns the response without waiting.
• Method [method: Response.httpVersion] returns the HTTP version used by the response.
• Option live in [method: Tracing.start] for real-time trace updates.
• Option artifacts_dir in [method: BrowserType.launch] to configure the artifacts directory.

New [method: Browser.bind] API makes a launched browser available for playwright-cli, @playwright/mcp, and other clients to connect to.

Bind a browser — start a browser and bind it so others can connect:

server_info = await browser.bind("my-session",
    workspace_dir="/my/project",
)

Connect from playwright-cli — connect to the running browser from your favorite coding agent.

playwright-cli attach my-session
playwright-cli -s my-session snapshot

Connect from @playwright/mcp — or point your MCP server to the running browser.

@playwright/mcp --endpoint=my-session

Connect from a Playwright client — use API to connect to the browser. Multiple clients at a time are supported!

browser = await chromium.connect(server_info["endpoint"])

Pass host and port options to bind over WebSocket instead of a named pipe:

server_info = await browser.bind("my-session",
    host="localhost",
    port=0,
)
# server_info["endpoint"] is a ws:// URL

Call [method: Browser.unbind] to stop accepting new connections.

Run playwright-cli show to open the Dashboard that lists all the bound browsers, their statuses, and allows interacting with them:

• See what your agent is doing on the background browsers
• Click into the sessions for manual interventions
• Open DevTools to inspect pages from the background browsers.

• playwright-cli binds all of its browsers automatically, so you can see what your agents are doing.
• Pass PLAYWRIGHT_DASHBOARD=1 env variable to see all @playwright/test browsers in the dashboard.

• Removed macOS 14 support for WebKit. We recommend upgrading your macOS version, or keeping an older Playwright version.

• Chromium 147.0.7727.15
• Mozilla Firefox 148.0.2
• WebKit 26.4

This version was also tested against the following stable channels:

• Google Chrome 146
• Microsoft Edge 146

• New 'system' theme option follows your OS dark/light mode preference
• Search functionality (Cmd/Ctrl+F) is now available in code editors
• Network details panel has been reorganized for better usability
• JSON responses are now automatically formatted for readability

Thanks to @cpAdm for contributing these improvements!

[method: BrowserType.connectOverCDP] now accepts an is_local option. When set to True, it tells Playwright that it runs on the same host as the CDP server, enabling file system optimizations.

• Removed _react and _vue selectors. See locators guide for alternatives.

• Removed :light selector engine suffix. Use standard CSS selectors instead.

• Option devtools from [method: BrowserType.launch] has been removed. Use args=['--auto-open-devtools-for-tabs'] instead.

• Removed macOS 13 support for WebKit. We recommend to upgrade your macOS version, or keep using an older Playwright version.

• Chromium 145.0.7632.6
• Mozilla Firefox 146.0.1
• WebKit 26.0

This version was also tested against the following stable channels:

• Google Chrome 144
• Microsoft Edge 144

Playwright now runs on Chrome for Testing builds rather than Chromium. Headed mode uses chrome; headless mode uses chrome-headless-shell. Existing tests should continue to pass after upgrading to v1.57.

We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.

If you still see an unexpected behaviour change, please file an issue.

On Arm64 Linux, Playwright continues to use Chromium.

After 3 years of being deprecated, we removed page.accessibility from our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.

• [event: Worker.console] event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. [method: Worker.waitForEvent] can be used to wait for it.
• [method: Locator.description] returns locator description previously set with [method: Locator.describe].
• New option [option: Locator.click.steps] in [method: Locator.click] and [method: Locator.dragTo] that configures the number of mousemove events emitted while moving the mouse pointer to the target element.
• Network requests issued by Service Workers are now reported and can be routed through the BrowserContext, only in Chromium. You can opt out using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK environment variable.
• Console messages from Service Workers are dispatched through [event: Worker.console]. You can opt out of this using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE environment variable.

• Chromium 143.0.7499.4
• Mozilla Firefox 144.0.2
• WebKit 26.0

• New methods [method: Page.consoleMessages] and [method: Page.pageErrors] for retrieving the most recent console messages from the page
• New method [method: Page.requests] for retrieving the most recent network requests from the page

• Event [event: BrowserContext.backgroundPage] has been deprecated and will not be emitted. Method [method: BrowserContext.backgroundPages] will return an empty list

• Aria snapshots render and compare input placeholder

• Chromium 141.0.7390.37
• Mozilla Firefox 142.0.1
• WebKit 26.0

• Automatic to_be_visible() assertions: Codegen can now generate automatic to_be_visible() assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.

• ⚠️ Dropped support for Chromium extension manifest v2.

• Added support for Debian 13 "Trixie".

• Chromium 140.0.7339.16
• Mozilla Firefox 141.0
• WebKit 26.0

This version was also tested against the following stable channels:

• Google Chrome 139
• Microsoft Edge 139

• New cookie property partition_key in [method: BrowserContext.cookies] and [method: BrowserContext.addCookies]. This property allows to save and restore partitioned cookies. See CHIPS MDN article for more information. Note that browsers have different support and defaults for cookie partitioning.

• New option --user-data-dir in multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.

  playwright codegen --user-data-dir=./user-data

• playwright open does not open the test recorder anymore. Use playwright codegen instead.

• Chromium 139.0.7258.5
• Mozilla Firefox 140.0.2
• WebKit 26.0

This version was also tested against the following stable channels:

• Google Chrome 140
• Microsoft Edge 140

• New Steps in Trace Viewer:
• New method [method: Locator.describe] to describe a locator. Used for trace viewer.

  button = page.get_by_test_id("btn-sub").describe("Subscribe button")
  button.click()

• python -m playwright install --list will now list all installed browsers, versions and locations.

• Chromium 138.0.7204.4
• Mozilla Firefox 139.0
• WebKit 18.5

This version was also tested against the following stable channels:

• Google Chrome 137
• Microsoft Edge 137

• New method [method: LocatorAssertions.toContainClass] to ergonomically assert individual class names on the element.

    expect(page.get_by_role('listitem', name='Ship v1.52')).to_contain_class('done')

• Aria Snapshots got two new properties: /children for strict matching and /url for links.

  expect(locator).to_match_aria_snapshot("""
    - list
      - /children: equal
      - listitem: Feature A
      - listitem:
        - link "Feature B":
          - /url: "https://playwright.dev"
  """)

• New option [option: APIRequest.newContext.maxRedirects] in [method: APIRequest.newContext] to control the maximum number of redirects.

• Glob URL patterns in methods like [method: Page.route] do not support ? and [] anymore. We recommend using regular expressions instead.
• Method [method: Route.continue] does not allow to override the Cookie header anymore. If a Cookie header is provided, it will be ignored, and the cookie will be loaded from the browser's cookie store. To set custom cookies, use [method: BrowserContext.addCookies].
• macOS 13 is now deprecated and will no longer receive WebKit updates. Please upgrade to a more recent macOS version to continue benefiting from the latest WebKit improvements.

• Chromium 136.0.7103.25
• Mozilla Firefox 137.0
• WebKit 18.4

This version was also tested against the following stable channels:

• Google Chrome 135
• Microsoft Edge 135

• New option [option: BrowserContext.storageState.indexedDB] for [method: BrowserContext.storageState] allows to save and restore IndexedDB contents. Useful when your application uses IndexedDB API to store authentication tokens, like Firebase Authentication.

  Here is an example following the authentication guide:

  # Save storage state into the file. Make sure to include IndexedDB.
  storage = await context.storage_state(path="state.json", indexed_db=True)
  
  # Create a new context with the saved storage state.
  context = await browser.new_context(storage_state="state.json")

• New option [option: Locator.filter.visible] for [method: Locator.filter] allows matching only visible elements.

  # Ignore invisible todo items.
  todo_items = page.get_by_test_id("todo-item").filter(visible=True)
  # Check there are exactly 3 visible ones.
  await expect(todo_items).to_have_count(3)

• New option contrast for methods [method: Page.emulateMedia] and [method: Browser.newContext] allows to emulate the prefers-contrast media feature.

• New option [option: APIRequest.newContext.failOnStatusCode] makes all fetch requests made through the [APIRequestContext] throw on response codes other than 2xx and 3xx.

• Chromium 134.0.6998.35
• Mozilla Firefox 135.0
• WebKit 18.4

This version was also tested against the following stable channels:

• Google Chrome 133
• Microsoft Edge 133

• Playwright's Pytest plugin now has support for Async Fixtures.

• Added method [method: LocatorAssertions.toHaveAccessibleErrorMessage] to assert the Locator points to an element with a given aria errormessage.

• New button in Codegen for picking elements to produce aria snapshots.
• Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
• Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
• Call and Network panels now display additional time information.

• [method: LocatorAssertions.toBeEditable] and [method: Locator.isEditable] now throw if the target element is not <input>, <select>, or a number of other editable elements.

• Chromium 133.0.6943.16
• Mozilla Firefox 134.0
• WebKit 18.2

This version was also tested against the following stable channels:

• Google Chrome 132
• Microsoft Edge 132

New assertion [method: LocatorAssertions.toMatchAriaSnapshot] verifies page structure by comparing to an expected accessibility tree, represented as YAML.

page.goto("https://playwright.dev")
expect(page.locator('body')).to_match_aria_snapshot('''
  - banner:
    - heading /Playwright enables reliable/ [level=1]
    - link "Get started"
    - link "Star microsoft/playwright on GitHub"
  - main:
    - img "Browsers (Chromium, Firefox, WebKit)"
    - heading "Any browser • Any platform • One API"
''')

You can generate this assertion with Test Generator or by calling [method: Locator.ariaSnapshot].

Learn more in the aria snapshots guide.

New method [method: Tracing.group] allows you to visually group actions in the trace viewer.

# All actions between group and group_end
# will be shown in the trace viewer as a group.
page.context.tracing.group("Open Playwright.dev > API")
page.goto("https://playwright.dev/")
page.get_by_role("link", name="API").click()
page.context.tracing.group_end()

This change affects you if you're using one of the following channels in your playwright.config.ts:

• chrome, chrome-dev, chrome-beta, or chrome-canary
• msedge, msedge-dev, msedge-beta, or msedge-canary

After updating to Playwright v1.49, run your test suite. If it still passes, you're good to go. If not, you will probably need to update your snapshots, and adapt some of your test code around PDF viewers and extensions. See issue #33566 for more details.

You can opt into the new headless mode by using 'chromium' channel. As official Chrome documentation puts it:

New Headless on the other hand is the real Chrome browser, and is thus more authentic, reliable, and offers more features. This makes it more suitable for high-accuracy end-to-end web app testing or browser extension testing.

See issue #33566 for the list of possible breakages you could encounter and more details on Chromium headless. Please file an issue if you see any problems after opting in.

pytest test_login.py --browser-channel chromium

• There will be no more updates for WebKit on Ubuntu 20.04 and Debian 11. We recommend updating your OS to a later version.
• <canvas> elements inside a snapshot now draw a preview.
• Python 3.8 is not supported anymore.

• Chromium 131.0.6778.33
• Mozilla Firefox 132.0
• WebKit 18.2

This version was also tested against the following stable channels:

• Google Chrome 130
• Microsoft Edge 130

New methods [method: Page.routeWebSocket] and [method: BrowserContext.routeWebSocket] allow to intercept, modify and mock WebSocket connections initiated in the page. Below is a simple example that mocks WebSocket communication by responding to a "request" with a "response".

def message_handler(ws: WebSocketRoute, message: Union[str, bytes]):
  if message == "request":
    ws.send("response")

page.route_web_socket("/ws", lambda ws: ws.on_message(
    lambda message: message_handler(ws, message)
))

See [WebSocketRoute] for more details.

• New "copy" buttons for annotations and test location in the HTML report.
• Route method calls like [method: Route.fulfill] are not shown in the report and trace viewer anymore. You can see which network requests were routed in the network tab instead.
• New "Copy as cURL" and "Copy as fetch" buttons for requests in the network tab.

• New method [method: Page.requestGC] may help detect memory leaks.
• Requests made by [APIRequestContext] now record detailed timing and security information in the HAR.

• Chromium 130.0.6723.19
• Mozilla Firefox 130.0
• WebKit 18.0

This version was also tested against the following stable channels:

• Google Chrome 129
• Microsoft Edge 129

The Network tab in the trace viewer has several nice improvements:

• filtering by asset type and URL
• better display of query string parameters
• preview of font assets

• The mcr.microsoft.com/playwright/python:v1.47.0 now serves a Playwright image based on Ubuntu 24.04 Noble. To use the 22.04 jammy-based image, please use mcr.microsoft.com/playwright/python:v1.47.0-jammy instead.
• The :latest/:focal/:jammy tag for Playwright Docker images is no longer being published. Pin to a specific version for better stability and reproducibility.
• TLS client certificates can now be passed from memory by passing [option: Browser.newContext.clientCertificates.cert] and [option: Browser.newContext.clientCertificates.key] as bytes instead of file paths.
• [option: Locator.selectOption.noWaitAfter] in [method: Locator.selectOption] was deprecated.
• We've seen reports of WebGL in Webkit misbehaving on GitHub Actions macos-13. We recommend upgrading GitHub Actions to macos-14.

• Chromium 129.0.6668.29
• Mozilla Firefox 130.0
• WebKit 18.0

This version was also tested against the following stable channels:

• Google Chrome 128
• Microsoft Edge 128

Playwright now allows to supply client-side certificates, so that server can verify them, as specified by TLS Client Authentication.

You can provide client certificates as a parameter of [method: Browser.newContext] and [method: APIRequest.newContext]. The following snippet sets up a client certificate for https://example.com:

context = browser.new_context(
    client_certificates=[
        {
            "origin": "https://example.com",
            "certPath": "client-certificates/cert.pem",
            "keyPath": "client-certificates/key.pem",
        }
    ],
)

• Content of text attachments is now rendered inline in the attachments pane.
• New setting to show/hide routing actions like [method: Route.continue].
• Request method and status are shown in the network details tab.
• New button to copy source file location to clipboard.
• Metadata pane now displays the base_url.

• New maxRetries option in [method: APIRequestContext.fetch] which retries on the ECONNRESET network error.

• Chromium 128.0.6613.18
• Mozilla Firefox 128.0
• WebKit 18.0

This version was also tested against the following stable channels:

• Google Chrome 127
• Microsoft Edge 127

Utilizing the new [Clock] API allows to manipulate and control time within tests to verify time-related behavior. This API covers many common scenarios, including:

• testing with predefined time;
• keeping consistent time and timers;
• monitoring inactivity;
• ticking through time manually.

# Initialize clock with some time before the test time and let the page load
# naturally. `Date.now` will progress as the timers fire.
page.clock.install(time=datetime.datetime(2024, 2, 2, 8, 0, 0))
page.goto("http://localhost:3333")

# Pretend that the user closed the laptop lid and opened it again at 10am.
# Pause the time once reached that point.
page.clock.pause_at(datetime.datetime(2024, 2, 2, 10, 0, 0))

# Assert the page state.
expect(page.get_by_test_id("current-time")).to_have_text("2/2/2024, 10:00:00 AM")

# Close the laptop lid again and open it at 10:30am.
page.clock.fast_forward("30:00")
expect(page.get_by_test_id("current-time")).to_have_text("2/2/2024, 10:30:00 AM")

See the clock guide for more details.

• Method [method: Locator.setInputFiles] now supports uploading a directory for <input type=file webkitdirectory> elements.

  page.get_by_label("Upload directory").set_input_files('mydir')

• Multiple methods like [method: Locator.click] or [method: Locator.press] now support a ControlOrMeta modifier key. This key maps to Meta on macOS and maps to Control on Windows and Linux.

  # Press the common keyboard shortcut Control+S or Meta+S to trigger a "Save" operation.
  page.keyboard.press("ControlOrMeta+S")

• New property httpCredentials.send in [method: APIRequest.newContext] that allows to either always send the Authorization header or only send it in response to 401 Unauthorized.

• Playwright now supports Chromium, Firefox and WebKit on Ubuntu 24.04.

• v1.45 is the last release to receive WebKit update for macOS 12 Monterey. Please update macOS to keep using the latest WebKit.

• Chromium 127.0.6533.5
• Mozilla Firefox 127.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 126
• Microsoft Edge 126

Accessibility assertions

• [method: LocatorAssertions.toHaveAccessibleName] checks if the element has the specified accessible name:

  locator = page.get_by_role("button")
  expect(locator).to_have_accessible_name("Submit")

• [method: LocatorAssertions.toHaveAccessibleDescription] checks if the element has the specified accessible description:

  locator = page.get_by_role("button")
  expect(locator).to_have_accessible_description("Upload a photo")

• [method: LocatorAssertions.toHaveRole] checks if the element has the specified ARIA role:

  locator = page.get_by_test_id("save-button")
  expect(locator).to_have_role("button")

Locator handler

• After executing the handler added with [method: Page.addLocatorHandler], Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new no_wait_after option.
• You can use new times option in [method: Page.addLocatorHandler] to specify maximum number of times the handler should be run.
• The handler in [method: Page.addLocatorHandler] now accepts the locator as argument.
• New [method: Page.removeLocatorHandler] method for removing previously added locator handlers.

locator = page.get_by_text("This interstitial covers the button")
page.add_locator_handler(locator, lambda overlay: overlay.locator("#close").click(), times=3, no_wait_after=True)
# Run your tests that can be interrupted by the overlay.
# ...
page.remove_locator_handler(locator)

Miscellaneous options

• [method: PageAssertions.toHaveURL] now supports ignore_case option.

• Chromium 125.0.6422.14
• Mozilla Firefox 125.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 124
• Microsoft Edge 124

• Method [method: BrowserContext.clearCookies] now supports filters to remove only some cookies.

  # Clear all cookies.
  context.clear_cookies()
  # New: clear cookies with a particular name.
  context.clear_cookies(name="session-id")
  # New: clear cookies for a particular domain.
  context.clear_cookies(domain="my-origin.com")

• New method [method: Locator.contentFrame] converts a [Locator] object to a [FrameLocator]. This can be useful when you have a [Locator] object obtained somewhere, and later on would like to interact with the content inside the frame.

  locator = page.locator("iframe[name='embedded']")
  # ...
  frame_locator = locator.content_frame
  frame_locator.getByRole("button").click()

• New method [method: FrameLocator.owner] converts a [FrameLocator] object to a [Locator]. This can be useful when you have a [FrameLocator] object obtained somewhere, and later on would like to interact with the iframe element.

  frame_locator = page.frame_locator("iframe[name='embedded']")
  # ...
  locator = frame_locator.owner
  expect(locator).to_be_visible()

• Conda builds are now published for macOS-arm64 and Linux-arm64.

• Chromium 124.0.6367.8
• Mozilla Firefox 124.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 123
• Microsoft Edge 123

New method [method: Page.addLocatorHandler] registers a callback that will be invoked when specified element becomes visible and may block Playwright actions. The callback can get rid of the overlay. Here is an example that closes a cookie dialog when it appears.

# Setup the handler.
page.add_locator_handler(
    page.get_by_role("heading", name="Hej! You are in control of your cookies."),
    lambda: page.get_by_role("button", name="Accept all").click(),
)
# Write the test as usual.
page.goto("https://www.ikea.com/")
page.get_by_role("link", name="Collection of blue and white").click()
expect(page.get_by_role("heading", name="Light and easy")).to_be_visible()

• [method: Page.pdf] accepts two new options [option: Page.pdf.tagged] and [option: Page.pdf.outline].

• ⚠️ Ubuntu 18 is not supported anymore.

• Chromium 123.0.6312.4
• Mozilla Firefox 123.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 122
• Microsoft Edge 123

• New method [method: Page.unrouteAll] removes all routes registered by [method: Page.route] and [method: Page.routeFromHAR]. Optionally allows to wait for ongoing routes to finish, or ignore any errors from them.
• New method [method: BrowserContext.unrouteAll] removes all routes registered by [method: BrowserContext.route] and [method: BrowserContext.routeFromHAR]. Optionally allows to wait for ongoing routes to finish, or ignore any errors from them.
• New options [option: Page.screenshot.style] in [method: Page.screenshot] and [option: Locator.screenshot.style] in [method: Locator.screenshot] to add custom CSS to the page before taking a screenshot.

• Chromium 121.0.6167.57
• Mozilla Firefox 121.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 120
• Microsoft Edge 120

New tools to generate assertions:

• "Assert visibility" tool generates [method: LocatorAssertions.toBeVisible].
• "Assert value" tool generates [method: LocatorAssertions.toHaveValue].
• "Assert text" tool generates [method: LocatorAssertions.toContainText].

Here is an example of a generated test with assertions:

from playwright.sync_api import Page, expect

def test_example(page: Page) -> None:
    page.goto("https://playwright.dev/")
    page.get_by_role("link", name="Get started").click()
    expect(page.get_by_label("Breadcrumbs").get_by_role("list")).to_contain_text("Installation")
    expect(page.get_by_label("Search")).to_be_visible()
    page.get_by_label("Search").click()
    page.get_by_placeholder("Search docs").fill("locator")
    expect(page.get_by_placeholder("Search docs")).to_have_value("locator");

• Options [option: Page.close.reason] in [method: Page.close], [option: BrowserContext.close.reason] in [method: BrowserContext.close] and [option: Browser.close.reason] in [method: Browser.close]. Close reason is reported for all operations interrupted by the closure.
• Option [option: BrowserType.launchPersistentContext.firefoxUserPrefs] in [method: BrowserType.launchPersistentContext].

• Method [method: Download.path] throws an error for failed and cancelled downloads.

• Chromium 120.0.6099.28
• Mozilla Firefox 119.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 119
• Microsoft Edge 119

Evergreen browsers update.

• Chromium 119.0.6045.9
• Mozilla Firefox 118.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 118
• Microsoft Edge 118

1. Zoom into time range.
2. Network panel redesign.

• [event: BrowserContext.webError]
• [method: Locator.pressSequentially]

• The following methods were deprecated: [method: Page.type], [method: Frame.type], [method: Locator.type] and [method: ElementHandle.type]. Please use [method: Locator.fill] instead which is much faster. Use [method: Locator.pressSequentially] only if there is a special keyboard handling on the page, and you need to press keys one-by-one.

• Chromium 117.0.5938.62
• Mozilla Firefox 117.0
• WebKit 17.0

This version was also tested against the following stable channels:

• Google Chrome 116
• Microsoft Edge 116

• New --full-page-screenshot command line flag allows taking a full page screenshot on failure.

• It is now possible to override the context options for a single test by using the browser_context_args marker.

• pytest-playwright is now also getting published on Anaconda

Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit. Let us know if you encounter any issues!

Linux support looks like this:

• Chromium 116.0.5845.82
• Mozilla Firefox 115.0
• WebKit 17.0

This version was also tested against the following stable channels:

• Google Chrome 115
• Microsoft Edge 115

🏝️ Summer maintenance release.

• Chromium 115.0.5790.75
• Mozilla Firefox 115.0
• WebKit 17.0

This version was also tested against the following stable channels:

• Google Chrome 114
• Microsoft Edge 114

• New option mask_color for methods [method: Page.screenshot] and [method: Locator.screenshot] to change default masking color.

• New uninstall CLI command to uninstall browser binaries:

  $ playwright uninstall # remove browsers installed by this installation
  $ playwright uninstall --all # remove all ever-install Playwright browsers

• Chromium 115.0.5790.13
• Mozilla Firefox 113.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 114
• Microsoft Edge 114

• New [method: Locator.and] to create a locator that matches both locators.

  button = page.get_by_role("button").and_(page.get_by_title("Subscribe"))

• New events [event: BrowserContext.console] and [event: BrowserContext.dialog] to subscribe to any dialogs and console messages from any page from the given browser context. Use the new methods [method: ConsoleMessage.page] and [method: Dialog.page] to pin-point event source.

• Chromium 114.0.5735.26
• Mozilla Firefox 113.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 113
• Microsoft Edge 113

• Use [method: Locator.or] to create a locator that matches either of the two locators. Consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly:

  new_email = page.get_by_role("button", name="New email")
  dialog = page.get_by_text("Confirm security settings")
  expect(new_email.or_(dialog)).is_visible()
  if (dialog.is_visible()):
    page.get_by_role("button", name="Dismiss").click()
  new_email.click()

• Use new options [option: Locator.filter.hasNot] and [option: Locator.filter.hasNotText] in [method: Locator.filter] to find elements that do not match certain conditions.

  row_locator = page.locator("tr")
  row_locator.filter(has_not_text="text in column 1").filter(
      has_not=page.get_by_role("button", name="column 2 button")
  ).screenshot()

• Use new web-first assertion [method: LocatorAssertions.toBeAttached] to ensure that the element is present in the page's DOM. Do not confuse with the [method: LocatorAssertions.toBeVisible] that ensures that element is both attached & visible.

• [method: Locator.or]
• New option [option: Locator.filter.hasNot] in [method: Locator.filter]
• New option [option: Locator.filter.hasNotText] in [method: Locator.filter]
• [method: LocatorAssertions.toBeAttached]
• New option [option: Route.fetch.timeout] in [method: Route.fetch]

• The mcr.microsoft.com/playwright/python:v1.33.0 now serves a Playwright image based on Ubuntu Jammy. To use the focal-based image, please use mcr.microsoft.com/playwright/python:v1.33.0-focal instead.

• Chromium 113.0.5672.53
• Mozilla Firefox 112.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 112
• Microsoft Edge 112

• Custom expect message, see test assertions documentation.
• New options [option: Page.routeFromHAR.updateMode] and [option: Page.routeFromHAR.updateContent] in [method: Page.routeFromHAR] and [method: BrowserContext.routeFromHAR].
• Chaining existing locator objects, see locator docs for details.
• New option [option: Tracing.startChunk.name] in method [method: Tracing.startChunk].

• Chromium 112.0.5615.29
• Mozilla Firefox 111.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 111
• Microsoft Edge 111

• New assertion [method: LocatorAssertions.toBeInViewport] ensures that locator points to an element that intersects viewport, according to the intersection observer API.

  from playwright.sync_api import expect
  
  locator = page.get_by_role("button")
  
  # Make sure at least some part of element intersects viewport.
  expect(locator).to_be_in_viewport()
  
  # Make sure element is fully outside of viewport.
  expect(locator).not_to_be_in_viewport()
  
  # Make sure that at least half of the element intersects viewport.
  expect(locator).to_be_in_viewport(ratio=0.5)

• DOM snapshots in trace viewer can be now opened in a separate window.
• New option [option: Route.fetch.maxRedirects] for method [method: Route.fetch].
• Playwright now supports Debian 11 arm64.
• Official docker images now include Node 18 instead of Node 16.

• Chromium 111.0.5563.19
• Mozilla Firefox 109.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 110
• Microsoft Edge 110

• Chromium 110.0.5481.38
• Mozilla Firefox 108.0.2
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 109
• Microsoft Edge 109

• New method [method: Route.fetch] and new option json for [method: Route.fulfill]:

  def handle_route(route: Route):
    # Fetch original settings.
    response = route.fetch()
  
    # Force settings theme to a predefined value.
    json = response.json()
    json["theme"] = "Solorized"
  
    # Fulfill with modified data.
    route.fulfill(json=json)
  
  
  page.route("**/api/settings", handle_route)

• New method [method: Locator.all] to iterate over all matching elements:

  # Check all checkboxes!
  checkboxes = page.get_by_role("checkbox")
  for checkbox in checkboxes.all():
    checkbox.check()

• [method: Locator.selectOption] matches now by value or label:

  <select multiple>
    <option value="red">Red</option>
    <option value="green">Green</option>
    <option value="blue">Blue</option>
  </select>

  element.select_option("Red")

• Option postData in method [method: Route.continue] now supports [Serializable] values.

• Chromium 109.0.5414.46
• Mozilla Firefox 107.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 108
• Microsoft Edge 108

• Live Locators in CodeGen. Generate a locator for any element on the page using "Explore" tool.

• [method: Locator.blur]
• [method: Locator.clear]

• Chromium 108.0.5359.29
• Mozilla Firefox 106.0
• WebKit 16.4

This version was also tested against the following stable channels:

• Google Chrome 107
• Microsoft Edge 107

With these new APIs writing locators is a joy:

• [method: Page.getByText] to locate by text content.
• [method: Page.getByRole] to locate by ARIA role, ARIA attributes and accessible name.
• [method: Page.getByLabel] to locate a form control by associated label's text.
• [method: Page.getByTestId] to locate an element based on its data-testid attribute (other attribute can be configured).
• [method: Page.getByPlaceholder] to locate an input by placeholder.
• [method: Page.getByAltText] to locate an element, usually image, by its text alternative.
• [method: Page.getByTitle] to locate an element by its title.

page.get_by_label("User Name").fill("John")

page.get_by_label("Password").fill("secret-password")

page.get_by_role("button", name="Sign in").click()

expect(page.get_by_text("Welcome, John!")).to_be_visible()

All the same methods are also available on [Locator], [FrameLocator] and [Frame] classes.

• As announced in v1.25, Ubuntu 18 will not be supported as of Dec 2022. In addition to that, there will be no WebKit updates on Ubuntu 18 starting from the next Playwright release.

• [method: LocatorAssertions.toHaveAttribute] with an empty value does not match missing attribute anymore. For example, the following snippet will succeed when button does not have a disabled attribute.

  expect(page.get_by_role("button")).to_have_attribute("disabled", "")

• Chromium 107.0.5304.18
• Mozilla Firefox 105.0.1
• WebKit 16.0

This version was also tested against the following stable channels:

• Google Chrome 106
• Microsoft Edge 106

• New option enabled for [method: LocatorAssertions.toBeEnabled].
• [method: LocatorAssertions.toHaveText] now pierces open shadow roots.
• New option editable for [method: LocatorAssertions.toBeEditable].
• New option visible for [method: LocatorAssertions.toBeVisible].

• New option max_redirects for [method: APIRequestContext.get] and others to limit redirect count.
• Python 3.11 is now supported.

A bunch of Playwright APIs already support the wait_until: "domcontentloaded" option. For example:

page.goto("https://playwright.dev", wait_until="domcontentloaded")

Prior to 1.26, this would wait for all iframes to fire the DOMContentLoaded event.

To align with web specification, the 'domcontentloaded' value only waits for the target frame to fire the 'DOMContentLoaded' event. Use wait_until="load" to wait for all iframes.

• Chromium 106.0.5249.30
• Mozilla Firefox 104.0
• WebKit 16.0

This version was also tested against the following stable channels:

• Google Chrome 105
• Microsoft Edge 105

• 🎁 We now ship Ubuntu 22.04 Jammy Jellyfish docker image: mcr.microsoft.com/playwright/python:v1.34.0-jammy.
• 🪦 This is the last release with macOS 10.15 support (deprecated as of 1.21).
• ⚠️ Ubuntu 18 is now deprecated and will not be supported as of Dec 2022.

• Chromium 105.0.5195.19
• Mozilla Firefox 103.0
• WebKit 16.0

This version was also tested against the following stable channels:

• Google Chrome 104
• Microsoft Edge 104

Playwright now supports Debian 11 Bullseye on x86_64 for Chromium, Firefox and WebKit. Let us know if you encounter any issues!

Linux support looks like this:

| | Ubuntu 20.04 | Ubuntu 22.04 | Debian 11 | :--- | :---: | :---: | :---: | :---: | | Chromium | ✅ | ✅ | ✅ | | WebKit | ✅ | ✅ | ✅ | | Firefox | ✅ | ✅ | ✅ |

We rewrote our Getting Started docs to be more end-to-end testing focused. Check them out on playwright.dev.

Now you can record network traffic into a HAR file and re-use this traffic in your tests.

To record network into HAR file:

npx playwright open --save-har=github.har.zip https://github.com/microsoft

Alternatively, you can record HAR programmatically:

context = await browser.new_context(record_har_path="github.har.zip")
# ... do stuff ...
await context.close()

context = browser.new_context(record_har_path="github.har.zip")
# ... do stuff ...
context.close()

Use the new methods [method: Page.routeFromHAR] or [method: BrowserContext.routeFromHAR] to serve matching responses from the HAR file:

await context.route_from_har("github.har.zip")

context.route_from_har("github.har.zip")

Read more in our documentation.

You can now use [method: Route.fallback] to defer routing to other handlers.

Consider the following example:

# Remove a header from all requests
async def remove_header_handler(route: Route) -> None:
    headers = await route.request.all_headers()
    if "if-none-match" in headers:
        del headers["if-none-match"]
    await route.fallback(headers=headers)

await page.route("**/*", remove_header_handler)

# Abort all images
async def abort_images_handler(route: Route) -> None:
    if route.request.resource_type == "image":
        await route.abort()
    else:
        await route.fallback()

await page.route("**/*", abort_images_handler)

# Remove a header from all requests
def remove_header_handler(route: Route) -> None:
    headers = route.request.all_headers()
    if "if-none-match" in headers:
        del headers["if-none-match"]
    route.fallback(headers=headers)

page.route("**/*", remove_header_handler)

# Abort all images
def abort_images_handler(route: Route) -> None:
    if route.request.resource_type == "image":
        route.abort()
    else:
        route.fallback()

page.route("**/*", abort_images_handler)

Note that the new methods [method: Page.routeFromHAR] and [method: BrowserContext.routeFromHAR] also participate in routing and could be deferred to.

• New method [method: LocatorAssertions.toHaveValues] that asserts all selected values of <select multiple> element.
• Methods [method: LocatorAssertions.toContainText] and [method: LocatorAssertions.toHaveText] now accept ignore_case option.

• If there's a service worker that's in your way, you can now easily disable it with a new context option service_workers:

  context = await browser.new_context(service_workers="block")
  page = await context.new_page()

  context = browser.new_context(service_workers="block")
  page = context.new_page()

• Using .zip path for recordHar context option automatically zips the resulting HAR:

  context = await browser.new_context(record_har_path="github.har.zip")

  context = browser.new_context(record_har_path="github.har.zip")

• If you intend to edit HAR by hand, consider using the "minimal" HAR recording mode that only records information that is essential for replaying:

  context = await browser.new_context(record_har_mode="minimal", record_har_path="har.har")

  context = browser.new_context(record_har_mode="minimal", record_har_path="har.har")

• Playwright now runs on Ubuntu 22 amd64 and Ubuntu 22 arm64.

• Role selectors that allow selecting elements by their ARIA role, ARIA attributes and accessible name.

  # Click a button with accessible name "log in"
  page.locator("role=button[name='log in']").click()

  Read more in our documentation.

• New [method: Locator.filter] API to filter an existing locator

  buttons = page.locator("role=button")
  # ...
  submit_button = buttons.filter(has_text="Submit")
  submit_button.click()

• Codegen now supports generating Pytest Tests

  

• New role selectors that allow selecting elements by their ARIA role, ARIA attributes and accessible name.

  # Click a button with accessible name "log in"
  await page.locator("role=button[name='log in']").click()

  # Click a button with accessible name "log in"
  page.locator("role=button[name='log in']").click()

  Read more in our documentation.

• New scale option in [method: Page.screenshot] for smaller sized screenshots.

• New caret option in [method: Page.screenshot] to control text caret. Defaults to "hide".

• The mcr.microsoft.com/playwright docker image no longer contains Python. Please use mcr.microsoft.com/playwright/python as a Playwright-ready docker image with pre-installed Python.
• Playwright now supports large file uploads (100s of MBs) via [method: Locator.setInputFiles] API.

• Chromium 101.0.4951.26
• Mozilla Firefox 98.0.2
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 100
• Microsoft Edge 100

• New options for methods [method: Page.screenshot], [method: Locator.screenshot] and [method: ElementHandle.screenshot]:
  • Option animations: "disabled" rewinds all CSS animations and transitions to a consistent state
  • Option mask: Locator[] masks given elements, overlaying them with pink #FF00FF boxes.
• Trace Viewer now shows API testing requests.
• [method: Locator.highlight] visually reveals element(s) for easier debugging.

• We now ship a designated Python docker image mcr.microsoft.com/playwright/python. Please switch over to it if you use Python. This is the last release that includes Python inside our javascript mcr.microsoft.com/playwright docker image.
• v1.20 is the last release to receive WebKit update for macOS 10.15 Catalina. Please update macOS to keep using latest & greatest WebKit!

• Chromium 101.0.4921.0
• Mozilla Firefox 97.0.1
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 99
• Microsoft Edge 99

• Locator now supports a has option that makes sure it contains another locator inside:

  await page.locator("article", has=page.locator(".highlight")).click()

  page.locator("article", has=page.locator(".highlight")).click()

  Read more in locator documentation

• New [method: Locator.page]

• [method: Page.screenshot] and [method: Locator.screenshot] now automatically hide blinking caret

• Playwright Codegen now generates locators and frame locators

• Chromium 100.0.4863.0
• Mozilla Firefox 96.0.1
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 98
• Microsoft Edge 98

Playwright for Python 1.18 introduces new API Testing that lets you send requests to the server directly from Python! Now you can:

• test your server API
• prepare server side state before visiting the web application in a test
• validate server side post-conditions after running some actions in the browser

To do a request on behalf of Playwright's Page, use new [property: Page.request] API:

# Do a GET request on behalf of page
res = await page.request.get("http://example.com/foo.json")

# Do a GET request on behalf of page
res = page.request.get("http://example.com/foo.json")

Read more in our documentation.

Playwright for Python 1.18 introduces Web-First Assertions.

Consider the following example:

from playwright.async_api import Page, expect

async def test_status_becomes_submitted(page: Page) -> None:
    # ..
    await page.locator("#submit-button").click()
    await expect(page.locator(".status")).to_have_text("Submitted")

from playwright.sync_api import Page, expect

def test_status_becomes_submitted(page: Page) -> None:
    # ..
    page.locator("#submit-button").click()
    expect(page.locator(".status")).to_have_text("Submitted")

Playwright will be re-testing the node with the selector .status until fetched Node has the "Submitted" text. It will be re-fetching the node and checking it over and over, until the condition is met or until the timeout is reached. You can pass this timeout as an option.

Read more in our documentation.

• [method: Locator.dragTo]

• Each locator can now be optionally filtered by the text it contains:

  await page.locator("li", has_text="my item").locator("button").click()

  page.locator("li", has_text="my item").locator("button").click()

  Read more in locator documentation

• accept_downloads option now defaults to True.
• sources option to embed sources into traces.

• Chromium 99.0.4812.0
• Mozilla Firefox 95.0
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 97
• Microsoft Edge 97

Playwright 1.17 introduces frame locators - a locator to the iframe on the page. Frame locators capture the logic sufficient to retrieve the iframe and then locate elements in that iframe. Frame locators are strict by default, will wait for iframe to appear and can be used in Web-First assertions.

Frame locators can be created with either [method: Page.frameLocator] or [method: Locator.frameLocator] method.

locator = page.frame_locator("my-frame").locator("text=Submit")
locator.click()

Read more at our documentation.

Playwright Trace Viewer is now available online at https://trace.playwright.dev! Just drag-and-drop your trace.zip file to inspect its contents.

NOTE: trace files are not uploaded anywhere; trace.playwright.dev is a progressive web application that processes traces locally.

• Playwright Test traces now include sources by default (these could be turned off with tracing option)
• Trace Viewer now shows test name
• New trace metadata tab with browser details
• Snapshots now have URL bar

• HTML report now supports dynamic filtering
• Report is now a single static HTML file that could be sent by e-mail or as a slack attachment.

• Playwright now supports Ubuntu 20.04 ARM64. You can now run Playwright tests inside Docker on Apple M1 and on Raspberry Pi.
• You can now use Playwright to install stable version of Edge on Linux:

  npx playwright install msedge

• Tracing now supports a 'title' option
• Page navigations support a new 'commit' waiting option

Wait for a locator to resolve to a single element with a given state. Defaults to the state: 'visible'.

Comes especially handy when working with lists:

order_sent = page.locator("#order-sent")
order_sent.wait_for()

Read more about [method: Locator.waitFor].

Playwright Docker image is now published for Arm64 so it can be used on Apple Silicon.

Read more about Docker integration.

• run trace viewer with npx playwright show-trace and drop trace files to the trace viewer PWA
• better visual attribution of action targets

Read more about Trace Viewer.

• Chromium 97.0.4666.0
• Mozilla Firefox 93.0
• WebKit 15.4

This version of Playwright was also tested against the following stable channels:

• Google Chrome 94
• Microsoft Edge 94

By using [method: Mouse.wheel] you are now able to scroll vertically or horizontally.

Previously it was not possible to get multiple header values of a response. This is now possible and additional helper functions are available:

• [method: Request.allHeaders]
• [method: Request.headersArray]
• [method: Request.headerValue]
• [method: Response.allHeaders]
• [method: Response.headersArray]
• [method: Response.headerValue]
• [method: Response.headerValues]

Its now possible to emulate the forced-colors CSS media feature by passing it in the [method: Browser.newContext] or calling [method: Page.emulateMedia].

• [method: Page.route] accepts new times option to specify how many times this route should be matched.
• [method: Page.setChecked] and [method: Locator.setChecked] were introduced to set the checked state of a checkbox.
• [method: Request.sizes] Returns resource size information for given http request.
• [method: Tracing.startChunk] - Start a new trace chunk.
• [method: Tracing.stopChunk] - Stops a new trace chunk.

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

Selector ambiguity is a common problem in automation testing. "strict" mode ensures that your selector points to a single element and throws otherwise.

Pass strict=true into your action calls to opt in.

# This will throw if you have more than one button!
page.click("button", strict=True)

Locator represents a view to the element(s) on the page. It captures the logic sufficient to retrieve the element at any given moment.

The difference between the Locator and ElementHandle is that the latter points to a particular element, while Locator captures the logic of how to retrieve that element.

Also, locators are "strict" by default!

locator = page.locator("button")
locator.click()

Learn more in the documentation.

React and Vue selectors allow selecting elements by its component name and/or property values. The syntax is very similar to attribute selectors and supports all attribute selector operators.

page.locator("_react=SubmitButton[enabled=true]").click()
page.locator("_vue=submit-button[enabled=true]").click()

Learn more in the react selectors documentation and the vue selectors documentation.

• nth selector engine is equivalent to the :nth-match pseudo class, but could be combined with other selector engines.
• visible selector engine is equivalent to the :visible pseudo class, but could be combined with other selector engines.

# select the first button among all buttons
button.click("button >> nth=0")
# or if you are using locators, you can use first, nth() and last
page.locator("button").first.click()

# click a visible button
button.click("button >> visible=true")

• Chromium 94.0.4595.0
• Mozilla Firefox 91.0
• WebKit 15.0

• 🖖 Programmatic drag-and-drop support via the [method: Page.dragAndDrop] API.
• 🔎 Enhanced HAR with body sizes for requests and responses. Use via recordHar option in [method: Browser.newContext].

• Playwright Trace Viewer now shows parameters, returned values and console.log() calls.

• Intro
• Authentication
• Chrome Extensions

• Chromium 93.0.4576.0
• Mozilla Firefox 90.0
• WebKit 14.2

• new baseURL option in [method: Browser.newContext] and [method: Browser.newPage]
• [method: Response.securityDetails] and [method: Response.serverAddr]
• [method: Page.dragAndDrop] and [method: Frame.dragAndDrop]
• [method: Download.cancel]
• [method: Page.inputValue], [method: Frame.inputValue] and [method: ElementHandle.inputValue]
• new force option in [method: Page.fill], [method: Frame.fill], and [method: ElementHandle.fill]
• new force option in [method: Page.selectOption], [method: Frame.selectOption], and [method: ElementHandle.selectOption]

Playwright Trace Viewer is a new GUI tool that helps exploring recorded Playwright traces after the script ran. Playwright traces let you examine:

• page DOM before and after each Playwright action
• page rendering before and after each Playwright action
• browser network during script execution

Traces are recorded using the new [property: BrowserContext.tracing] API:

browser = chromium.launch()
context = browser.new_context()

# Start tracing before creating / navigating a page.
context.tracing.start(screenshots=True, snapshots=True)

page.goto("https://playwright.dev")

# Stop tracing and export it into a zip archive.
context.tracing.stop(path = "trace.zip")

Traces are examined later with the Playwright CLI:

playwright show-trace trace.zip

That will open the following GUI:

👉 Read more in trace viewer documentation.

• Chromium 93.0.4530.0
• Mozilla Firefox 89.0
• WebKit 14.2

This version of Playwright was also tested against the following stable channels:

• Google Chrome 91
• Microsoft Edge 91

• reducedMotion option in [method: Page.emulateMedia], [method: BrowserType.launchPersistentContext], [method: Browser.newContext] and [method: Browser.newPage]
• [event: BrowserContext.request]
• [event: BrowserContext.requestFailed]
• [event: BrowserContext.requestFinished]
• [event: BrowserContext.response]
• tracesDir option in [method: BrowserType.launch] and [method: BrowserType.launchPersistentContext]
• new [property: BrowserContext.tracing] API namespace
• new [method: Download.page] method

🎥 New video: Playwright: A New Test Automation Framework for the Modern Web (slides)

• We talked about Playwright
• Showed engineering work behind the scenes
• Did live demos with new features ✨
• Special thanks to applitools for hosting the event and inviting us!

• Chromium 92.0.4498.0
• Mozilla Firefox 89.0b6
• WebKit 14.2

• support for async predicates across the API in methods such as [method: Page.waitForRequest] and others
• new emulation devices: Galaxy S8, Galaxy S9+, Galaxy Tab S4, Pixel 3, Pixel 4
• new methods:
  • [method: Page.waitForURL] to await navigations to URL
  • [method: Video.delete] and [method: Video.saveAs] to manage screen recording
• new options:
  • screen option in the [method: Browser.newContext] method to emulate window.screen dimensions
  • position option in [method: Page.check] and [method: Page.uncheck] methods
  • trial option to dry-run actions in [method: Page.check], [method: Page.uncheck], [method: Page.click], [method: Page.dblclick], [method: Page.hover] and [method: Page.tap]

• Playwright for Java v1.10 is now stable!
• Run Playwright against Google Chrome and Microsoft Edge stable channels with the new channels API.
• Chromium screenshots are fast on Mac & Windows.

• Chromium 90.0.4430.0
• Mozilla Firefox 87.0b10
• WebKit 14.2

This version of Playwright was also tested against the following stable channels:

• Google Chrome 89
• Microsoft Edge 89

• [method: BrowserType.launch] now accepts the new 'channel' option. Read more in our documentation.

• Playwright Inspector is a new GUI tool to author and debug your tests.

  • Line-by-line debugging of your Playwright scripts, with play, pause and step-through.
  • Author new scripts by recording user actions.
  • Generate element selectors for your script by hovering over elements.
  • Set the PWDEBUG=1 environment variable to launch the Inspector

• Pause script execution with [method: Page.pause] in headed mode. Pausing the page launches Playwright Inspector for debugging.

• New has-text pseudo-class for CSS selectors. :has-text("example") matches any element containing "example" somewhere inside, possibly in a child or a descendant element. See more examples.

• Page dialogs are now auto-dismissed during execution, unless a listener for dialog event is configured. Learn more about this.

• Playwright for Python is now stable with an idiomatic snake case API and pre-built Docker image to run tests in CI/CD.

• Chromium 90.0.4421.0
• Mozilla Firefox 86.0b10
• WebKit 14.1

• [method: Page.pause].

• Selecting elements based on layout with :left-of(), :right-of(), :above() and :below().
• Playwright now includes command line interface, former playwright-cli.

  playwright --help

• [method: Page.selectOption] now waits for the options to be present.
• New methods to assert element state like [method: Page.isEditable].

• [method: ElementHandle.isChecked].
• [method: ElementHandle.isDisabled].
• [method: ElementHandle.isEditable].
• [method: ElementHandle.isEnabled].
• [method: ElementHandle.isHidden].
• [method: ElementHandle.isVisible].
• [method: Page.isChecked].
• [method: Page.isDisabled].
• [method: Page.isEditable].
• [method: Page.isEnabled].
• [method: Page.isHidden].
• [method: Page.isVisible].
• New option 'editable' in [method: ElementHandle.waitForElementState].

• Chromium 90.0.4392.0
• Mozilla Firefox 85.0b5
• WebKit 14.1

• New Java SDK: Playwright for Java is now on par with JavaScript, Python and .NET bindings.
• Browser storage API: New convenience APIs to save and load browser storage state (cookies, local storage) to simplify automation scenarios with authentication.
• New CSS selectors: We heard your feedback for more flexible selectors and have revamped the selectors implementation. Playwright 1.7 introduces new CSS extensions and there's more coming soon.
• New website: The docs website at playwright.dev has been updated and is now built with Docusaurus.
• Support for Apple Silicon: Playwright browser binaries for WebKit and Chromium are now built for Apple Silicon.

• [method: BrowserContext.storageState] to get current state for later reuse.
• storageState option in [method: Browser.newContext] and [method: Browser.newPage] to setup browser context state.

• Chromium 89.0.4344.0
• Mozilla Firefox 84.0b9
• WebKit 14.1