Update playwright-dotnet monorepo to 1.59.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.Playwright	1.45.0 → 1.59.0
Microsoft.Playwright.TestAdapter	1.45.0 → 1.59.0

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.

---

Release Notes

microsoft/playwright-dotnet (Microsoft.Playwright)

v1.59.0

🎬 Screencast

New 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 recordVideoDir option:

await page.Screencast.StartAsync(new() { Path = "video.webm" });
// ... perform actions ...
await page.Screencast.StopAsync();

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

await page.Screencast.ShowActionsAsync(new() { Position = "top-right" });

ShowActionsAsync accepts Position ("top-left", "top", "top-right", "bottom-left", "bottom", "bottom-right"), Duration (ms per annotation), and FontSize (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:

await page.Screencast.ShowChapterAsync("Adding TODOs", new() {
    Description = "Type and press enter for each TODO",
    Duration = 1000,
});

await page.Screencast.ShowOverlayAsync("<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:

await page.Screencast.StartAsync(new() {
    OnFrame = frame => SendToVisionModel(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:

await page.Screencast.StartAsync(new() { Path = "receipt.webm" });
await page.Screencast.ShowActionsAsync(new() { Position = "top-right" });

await page.Screencast.ShowChapterAsync("Verifying checkout flow", new() {
    Description = "Added coupon code support per ticket #​1234",
});

// Agent performs the verification steps...
await page.Locator("#coupon").FillAsync("SAVE20");
await page.Locator("#apply-coupon").ClickAsync();
await Expect(page.Locator(".discount")).ToContainTextAsync("20%");

await page.Screencast.ShowChapterAsync("Done", new() {
    Description = "Coupon applied, discount reflected in total",
});

await page.Screencast.StopAsync();

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.

🔍 Snapshots and Locators

• Method Page.AriaSnapshotAsync() to capture the aria snapshot of the page — equivalent to Page.Locator("body").AriaSnapshotAsync().
• Options Depth and Mode in Locator.AriaSnapshotAsync().
• Method Locator.NormalizeAsync() converts a locator to follow best practices like test ids and aria roles.
• Method Page.PickLocatorAsync() enters an interactive mode where hovering over elements highlights them and shows the corresponding locator. Click an element to get its Locator back. Use Page.CancelPickLocatorAsync() to cancel.

New APIs

Screencast

• Page.Screencast provides video recording, real-time frame streaming, and overlay management.
• Methods Screencast.StartAsync() and screencast.stop() for recording and frame capture.
• Methods Screencast.ShowActionsAsync() and Screencast.HideActionsAsync() for action annotations.
• Methods Screencast.ShowChapterAsync() and Screencast.ShowOverlayAsync() for visual overlays.
• Methods Screencast.ShowOverlaysAsync() and Screencast.HideOverlaysAsync() for overlay visibility control.

Storage, Console and Errors

• Method BrowserContext.SetStorageStateAsync() clears existing cookies, local storage, and IndexedDB for all origins and sets a new storage state — no need to create a new context.
• Methods Page.ClearConsoleMessagesAsync() and page.clearPageErrors() to clear stored messages and errors.
• Option Filter in Page.ConsoleMessagesAsync() and page.pageErrors() controls which messages are returned.
• Proeprty ConsoleMessage.Timestamp.

Miscellaneous

• BrowserContext.Debugger provides programmatic control over the Playwright debugger.
• Property BrowserContext.IsClosed.
• Property Request.ExistingResponse returns the response without waiting.
• Method Response.HttpVersionAsync() returns the HTTP version used by the response.
• Option Live in Tracing.StartAsync() for real-time trace updates.
• Option ArtifactsDir in BrowserType.LaunchAsync() to configure the artifacts directory.

🔗 Interoperability

New Browser.BindAsync() 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:

var serverInfo = await browser.BindAsync("my-session", new() {
    WorkspaceDir = "/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!

var browser = await chromium.ConnectAsync(serverInfo.Endpoint);

Pass Host and Port options to bind over WebSocket instead of a named pipe:

var serverInfo = await browser.BindAsync("my-session", new() {
    Host = "localhost",
    Port = 0,
});
// serverInfo.Endpoint is a ws:// URL

Call Browser.UnbindAsync() to stop accepting new connections.

Run npx 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.

Breaking Changes ⚠️

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

Browser Versions

• 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

v1.58.0

Trace Viewer Improvements

• 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!

Miscellaneous

BrowserType.ConnectOverCDPAsync() now accepts an IsLocal option. When set to true, it tells Playwright that it runs on the same host as the CDP server, enabling file system optimizations.

Breaking Changes ⚠️

• Removed _react and _vue selectors. See locators guide for alternatives.
• Removed :light selector engine suffix. Use standard CSS selectors instead.
• Option Devtools from BrowserType.LaunchAsync() has been removed. Use Args = new[] { "--auto-open-devtools-for-tabs" } instead.
• Removed macOS 13 support for WebKit.

Browser Versions

• Chromium 145.0.7632.6
• Mozilla Firefox 146.0.1
• WebKit 26.0

v1.57.0

Chrome for Testing

Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.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.

Breaking Change

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.

New APIs

• Worker.Console event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir.
• Locator.Description returns locator description previously set with Locator.Describe().
• New option Steps in Locator.ClickAsync() and Locator.DragToAsync() that configures the number of mousemove events emitted while moving the mouse pointer to the target element.

Browser Versions

• Chromium 143.0.7499.4
• Mozilla Firefox 144.0.2
• WebKit 26.0

v1.56.0

New APIs

• New methods Page.ConsoleMessagesAsync() and Page.PageErrorsAsync() for retrieving the most recent console messages from the page
• New method Page.RequestsAsync() for retrieving the most recent network requests from the page

Breaking Changes

• Event BrowserContext.BackgroundPage has been deprecated and will not be emitted. Property BrowserContext.BackgroundPages will return an empty list

Miscellaneous

• Aria snapshots render and compare input placeholder

Browser Versions

• Chromium 141.0.7390.37
• Mozilla Firefox 142.0.1
• WebKit 26.0

v1.55.0

Codegen

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

Breaking Changes

• ⚠️ Dropped support for Chromium extension manifest v2.

Miscellaneous

• Added support for Debian 13 "Trixie".
• Added support for Xunit v3 as part of Microsoft.Playwright.Xunit.v3
• Added support for MSTest v4 as part of Microsoft.Playwright.MSTest.v4

Browser Versions

• 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

v1.54.0

Highlights

• New cookie property PartitionKey in browserContext.cookies() and 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.

  pwsh bin/Debug/netX/playwright.ps1 codegen --user-data-dir=./user-data

• pwsh bin/Debug/netX/playwright.ps1 open does not open the test recorder anymore. Use pwsh bin/Debug/netX/playwright.ps1 codegen instead.

Browser Versions

• 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

v1.53.0

Miscellaneous

• New Steps in Trace Viewer:

• New method Locator.Describe() to describe a locator. Used for trace viewer.

  var button = Page.GetByTestId("btn-sub").Describe("Subscribe button");
  await button.ClickAsync();

• pwsh bin/Debug/netX/playwright.ps1 install --list will now list all installed browsers, versions and locations.

Browser Versions

• 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

v1.52.0

Highlights

• New method Expect(locator).ToContainClassAsync() to ergonomically assert individual class names on the element.

    await Expect(Page.GetByRole(AriaRole.Listitem, new() { Name = "Ship v1.52" })).ToContainClassAsync("done");

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

  await Expect(locator).ToMatchAriaSnapshotAsync(@​"
    - list
      - /children: equal
      - listitem: Feature A
      - listitem:
        - link ""Feature B"":
          - /url: ""https://playwright.dev""
  ");

Miscellaneous

• New option MaxRedirects in apiRequest.NewContextAsync() to control the maximum number of redirects.
• New option Ref in locator.AriaSnapshotAsync() to generate reference for each element in the snapshot which can later be used to locate the element.

Breaking Changes

• Method route.ContinueAsync() 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 browserContext.AddCookiesAsync().
• 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.

Browser Versions

• 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

v1.51.0

Highlights

• New option IndexedDB for BrowserContext.StorageStateAsync() 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.
  await context.StorageStateAsync(new()
  {
      Path = "../../../playwright/.auth/state.json",
      IndexedDB = true
  });
  
  // Create a new context with the saved storage state.
  var context = await browser.NewContextAsync(new()
  {
      StorageStatePath = "../../../playwright/.auth/state.json"
  });

• New option Visible for locator.filter() allows matching only visible elements.

  // Ignore invisible todo items.
  var todoItems = Page.GetByTestId("todo-item").Filter(new() { Visible = true });
  // Check there are exactly 3 visible ones.
  await Expect(todoItems).ToHaveCountAsync(3);

• New option Contrast for methods page.emulateMedia() and Browser.NewContextAsync() allows to emulate the prefers-contrast media feature.

• New option FailOnStatusCode makes all fetch requests made through the APIRequestContext throw on response codes other than 2xx and 3xx.

Browser Versions

• 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

v1.50.0

Support for Xunit

• Support for xUnit 2.8+ via Microsoft.Playwright.Xunit. Follow our Getting Started guide to learn more.

Miscellaneous

• Added method Expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.

UI updates

• 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.

Breaking

• Expect(locator).toBeEditable() and locator.isEditable() now throw if the target element is not <input>, <select>, or a number of other editable elements.

Browser Versions

• 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

v1.49.0

Aria snapshots

New assertion Expect(locator).toMatchAriaSnapshot() verifies page structure by comparing to an expected accessibility tree, represented as YAML.

await page.GotoAsync("https://playwright.dev");
await Expect(page.Locator("body")).ToMatchAriaSnapshotAsync(@​"
  - 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 locator.ariaSnapshot().

Learn more in the aria snapshots guide.

Tracing groups

New method tracing.group() allows you to visually group actions in the trace viewer.

// All actions between GroupAsync and GroupEndAsync
// will be shown in the trace viewer as a group.
await Page.Context.Tracing.GroupAsync("Open Playwright.dev > API");
await Page.GotoAsync("https://playwright.dev/");
await Page.GetByRole(AriaRole.Link, new() { Name = "API" }).ClickAsync();
await Page.Context.Tracing.GroupEndAsync();

Breaking: chrome and msedge channels switch to new headless mode

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.

Try new Chromium headless

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.

// runsettings.xml
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
  <Playwright>
    <BrowserName>chromium</BrowserName>
    <LaunchOptions>
      <Channel>chromium</Channel>
    </LaunchOptions>
  </Playwright>
</RunSettings>

dotnet test -- Playwright.BrowserName=chromium Playwright.LaunchOptions.Channel=chromium

Miscellaneous

• 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.

Browser Versions

• 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

v1.48.0

WebSocket routing

New methods Page.RouteWebSocketAsync() and BrowserContext.RouteWebSocketAsync() 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".

await page.RouteWebSocketAsync("/ws", ws => {
  ws.OnMessage(message => {
    if (message.Text == "request")
      ws.Send("response");
  });
});

See WebSocketRoute for more details.

UI updates

• New "copy" buttons for annotations and test location in the HTML report.
• Route method calls like Foute.FulfillAsync() 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.

Miscellaneous

• New method Page.RequestGCAsync() may help detect memory leaks.
• Requests made by APIRequestContext now record detailed timing and security information in the HAR.

Browser Versions

• 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

v1.47.0

Network Tab improvements

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

Miscellaneous

• The mcr.microsoft.com/playwright/dotnet: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/dotnet: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 cert and key as byte arrays instead of file paths.
• NoWaitAfter in 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.

Browser Versions

• 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

v1.46.0

TLS Client Certificates

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 browser.NewContextAsync() and APIRequest.NewContextAsync(). The following snippet sets up a client certificate for https://example.com:

var context = await Browser.NewContextAsync(new() {
  ClientCertificates = [
    new() {
      Origin = "https://example.com",
      CertPath = "client-certificates/cert.pem",
      KeyPath = "client-certificates/key.pem",
    }
  ]
});

When using the MSTest or NUnit base-classes, these can be added by using the ContextOptions method.

Trace Viewer Updates

• Content of text attachments is now rendered inline in the attachments pane.
• New setting to show/hide routing actions like route.ContinueAsync().
• 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 BaseURL.

Miscellaneous

• New MaxRetries option in apiRequestContext.FetchAsync() which retries on the ECONNRESET network error.

Browser Versions

• 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

v1.45.1

Highlights

microsoft/playwright-java#1617 - [Bug]: Trace Viewer not reporting all actions
microsoft/playwright#31764 - [Bug]: some actions do not appear in the trace file

Browser Versions

• 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

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • "on the 1st through 7th day of the month"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

This diff updates Microsoft.Playwright and Microsoft.Playwright.TestAdapter from version 1.45.0 to 1.57.0 in the test project. This is a significant version jump spanning 12 minor releases with multiple breaking changes that could affect existing test code. The update likely aims to access newer features and browser versions, but requires careful validation to ensure compatibility with the existing test suite.

View this review on Amp

[github-actions]

This is a major version jump (1.45.0 → 1.57.0) with multiple breaking changes that should be tested:

1. Version 1.52: Glob URL patterns in RouteAsync() no longer support ? and [] - requires regex instead
2. Version 1.52: Route.ContinueAsync() no longer allows overriding Cookie header
3. Version 1.49: Chrome/Edge channels switched to new headless mode (may require snapshot updates)
4. Version 1.38: TypeAsync() methods deprecated in favor of Locator.FillAsync()

Verify that existing tests still pass and consider auditing test code for use of these deprecated/changed APIs before merging.

[github-actions]

Test Results

27 tests  ±0   22 ✅  - 4   14m 54s ⏱️ -8s
 1 suites ±0    1 💤 ±0 
 1 files   ±0    4 ❌ +4 

For more details on these failures, see this check.

Results for commit fb7c84a. ± Comparison against base commit 4db9c71.

♻️ This comment has been updated with latest results.