--- id: release-notes title: "Release notes" toc_max_heading_level: 2 --- ## Version 1.33 ### Locators Update * 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: ```csharp var newEmail = page.GetByRole(AriaRole.Button, new() { Name = "New" }); var dialog = page.GetByText("Confirm security settings"); await Expect(newEmail.Or(dialog)).ToBeVisibleAsync(); if (await dialog.IsVisibleAsync()) await page.GetByRole(AriaRole.Button, new () { Name = "Dismiss" }).ClickAsync(); await newEmail.ClickAsync(); ``` * Use new options [`option: hasNot`] and [`option: hasNotText`] in [`method: Locator.filter`] to find elements that **do not match** certain conditions. ```csharp var rowLocator = page.Locator("tr"); await rowLocator .Filter(new () { HasNotText = "text in column 1" }) .Filter(new () { HasNot = page.GetByRole(AriaRole.Button, new () { Name = "column 2 button" })) .ScreenshotAsync(); ``` * 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. ### New APIs - [`method: Locator.or`] - New option [`option: hasNot`] in [`method: Locator.filter`] - New option [`option: hasNotText`] in [`method: Locator.filter`] - [`method: LocatorAssertions.toBeAttached`] - New option [`option: timeout`] in [`method: Route.fetch`] ### ⚠ïļ Breaking change * The `mcr.microsoft.com/playwright/dotnet:v1.34.0` now serves a Playwright image based on Ubuntu Jammy. To use the focal-based image, please use `mcr.microsoft.com/playwright/dotnet:v1.34.0-focal` instead. ### Browser Versions * 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 ## Version 1.32 ### New APIs - New options [`option: updateMode`] and [`option: updateContent`] in [`method: Page.routeFromHAR`] and [`method: BrowserContext.routeFromHAR`]. - Chaining existing locator objects, see [locator docs](./locators.md#chaining-locators) for details. - New option [`option: name`] in method [`method: Tracing.startChunk`]. ### Browser Versions * 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 ## Version 1.31 ### New APIs - New assertion [`method: LocatorAssertions.toBeInViewport`] ensures that locator points to an element that intersects viewport, according to the [intersection observer API](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API). ```csharp var locator = Page.GetByRole(AriaRole.Button); // Make sure at least some part of element intersects viewport. await Expect(locator).ToBeInViewportAsync(); // Make sure element is fully outside of viewport. await Expect(locator).Not.ToBeInViewportAsync(); // Make sure that at least half of the element intersects viewport. await Expect(locator).ToBeInViewportAsync(new() { Ratio = 0.5 }); ``` - New methods [`method: BrowserContext.newCDPSession`] and [`method: Browser.newBrowserCDPSession`] create a [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) session for the page and browser respectively. ### Miscellaneous - 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](./docker.md) now include Node 18 instead of Node 16. ### Browser Versions * 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 ## Version 1.30 ### Browser Versions * 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 ## Version 1.29 ### New APIs - New method [`method: Route.fetch`] and new option `Json` for [`method: Route.fulfill`]: ```csharp await Page.RouteAsync("**/api/settings", async route => { // Fetch original settings. var response = await route.FetchAsync(); // Force settings theme to a predefined value. var json = await response.JsonAsync(); json.Theme = "Solarized"; // Fulfill with modified data. await route.FulfillAsync(new() { Json = json }); }); ``` - New method [`method: Locator.all`] to iterate over all matching elements: ```csharp // Check all checkboxes! var checkboxes = Page.GetByRole(AriaRole.Checkbox); foreach (var checkbox in await checkboxes.AllAsync()) await checkbox.CheckAsync(); ``` - [`method: Locator.selectOption`] matches now by value or label: ```html ``` ```csharp await element.SelectOptionAsync("Red"); ``` ### Browser Versions * 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 ## Version 1.28 ### Playwright Tools * **Live Locators in CodeGen.** Generate a locator for any element on the page using "Explore" tool. ![Locator Explorer](https://user-images.githubusercontent.com/9798949/202293757-2e3ec0ac-1feb-4d6f-9935-73e08658b76d.png) ### New APIs - [`method: Locator.blur`] - [`method: Locator.clear`] ### Browser Versions * 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 ## Version 1.27 ### Locators 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](https://www.w3.org/TR/wai-aria-1.2/#roles), [ARIA attributes](https://www.w3.org/TR/wai-aria-1.2/#aria-attributes) and [accessible name](https://w3c.github.io/accname/#dfn-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. ```csharp await page.GetByLabel("User Name").FillAsync("John"); await page.GetByLabel("Password").FillAsync("secret-password"); await page.GetByRole(AriaRole.Button, new() { NameString = "Sign in" }).ClickAsync(); await Expect(page.GetByText("Welcome, John!")).ToBeVisibleAsync(); ``` All the same methods are also available on [Locator], [FrameLocator] and [Frame] classes. ### Other highlights - 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. ### Behavior Changes - [`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. ```csharp await Expect(page.GetByRole(AriaRole.Button)).ToHaveAttribute("disabled", ""); ``` ### Browser Versions * 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 ## Version 1.26 ### Assertions - 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`]. - [`method: APIResponseAssertions.toBeOK`] is now available. ### Other highlights - New option `MaxRedirects` for [`method: APIRequestContext.get`] and others to limit redirect count. - Codegen now supports NUnit and MSTest frameworks. - ASP .NET is now supported. ### Behavior Change A bunch of Playwright APIs already support the `WaitUntil: WaitUntilState.DOMContentLoaded` option. For example: ```csharp await Page.GotoAsync("https://playwright.dev", new() { WaitUntil = WaitUntilState.DOMContentLoaded }); ``` Prior to 1.26, this would wait for all iframes to fire the `DOMContentLoaded` event. To align with web specification, the `WaitUntilState.DOMContentLoaded` value only waits for the target frame to fire the `'DOMContentLoaded'` event. Use `WaitUntil: WaitUntilState.Load` to wait for all iframes. ### Browser Versions * 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 ## Version 1.25 ### New .runsettings file support `Microsoft.Playwright.NUnit` and `Microsoft.Playwright.MSTest` will now consider the `.runsettings` file and passed settings via the CLI when running end-to-end tests. See in the [documentation](https://playwright.dev/dotnet/docs/test-runners) for a full list of supported settings. The following does now work: ```xml chromium 5000 true msedge pw:api ``` ### Announcements * ðŸŠĶ 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. ### Browser Versions * 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 ## Version 1.24
### 🐂 Debian 11 Bullseye Support 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 | ✅ | ✅ | ✅ | ### New introduction docs We rewrote our Getting Started docs to be more end-to-end testing focused. Check them out on [playwright.dev](https://playwright.dev/dotnet/docs/intro). ## Version 1.23 ### API Testing Playwright for .NET 1.23 introduces new [API Testing](./api/class-apirequestcontext) that lets you send requests to the server directly from .NET! 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**: ```csharp // Do a GET request on behalf of page var response = await Page.APIRequest.GetAsync("http://example.com/foo.json"); Console.WriteLine(response.Status); Console.WriteLine(response.StatusText); Console.WriteLine(response.Ok); Console.WriteLine(response.Headers["Content-Type"]); Console.WriteLine(await response.TextAsync()); Console.WriteLine((await response.JsonAsync())?.GetProperty("foo").GetString()); ``` Read more about it in our [API testing guide](./api-testing). ### Network Replay Now you can record network traffic into a HAR file and re-use this traffic in your tests. To record network into HAR file: ```bash pwsh bin/Debug/netX/playwright.ps1 open --save-har=example.har --save-har-glob="**/api/**" https://example.com ``` Alternatively, you can record HAR programmatically: ```csharp var context = await browser.NewContextAsync(new() { RecordHarPath = harPath, RecordHarUrlFilterString = "**/api/**", }); // ... Perform actions ... // Close context to ensure HAR is saved to disk. context.CloseAsync(); ``` Use the new methods [`method: Page.routeFromHAR`] or [`method: BrowserContext.routeFromHAR`] to serve matching responses from the [HAR](http://www.softwareishard.com/blog/har-12-spec/) file: ```csharp await context.RouteFromHARAsync("example.har"); ``` Read more in [our documentation](./network#record-and-replay-requests). ### Advanced Routing You can now use [`method: Route.fallback`] to defer routing to other handlers. Consider the following example: ```csharp // Remove a header from all requests. await page.RouteAsync("**/*", async route => { var headers = route.Request.Headers; headers.Remove("X-Secret"); await route.ContinueAsync(new() { Headers = headers }); }); // Abort all images. await page.RouteAsync("**/*", async route => { if (route.Request.ResourceType == "image") { await route.AbortAsync(); } else { await route.FallbackAsync(); } }); ``` Note that the new methods [`method: Page.routeFromHAR`] and [`method: BrowserContext.routeFromHAR`] also participate in routing and could be deferred to. ### Web-First Assertions Update * New method [`method: LocatorAssertions.toHaveValues`] that asserts all selected values of `