From 8eed00fa0e5a04e5663bbbd448f81cedc342e934 Mon Sep 17 00:00:00 2001 From: "microsoft-playwright-automation[bot]" <203992400+microsoft-playwright-automation[bot]@users.noreply.github.com> Date: Mon, 9 Feb 2026 10:30:36 +0000 Subject: [PATCH] feat(roll): roll to ToT Playwright (09-02-26) --- dotnet/docs/api/class-frame.mdx | 4 ++-- dotnet/docs/api/class-framelocator.mdx | 4 ++-- dotnet/docs/api/class-locator.mdx | 4 ++-- dotnet/docs/api/class-page.mdx | 4 ++-- java/docs/api/class-frame.mdx | 4 ++-- java/docs/api/class-framelocator.mdx | 4 ++-- java/docs/api/class-locator.mdx | 4 ++-- java/docs/api/class-page.mdx | 4 ++-- nodejs/docs/api/class-frame.mdx | 4 ++-- nodejs/docs/api/class-framelocator.mdx | 4 ++-- nodejs/docs/api/class-locator.mdx | 4 ++-- nodejs/docs/api/class-page.mdx | 4 ++-- nodejs/docs/ci.mdx | 20 ++++++++++---------- nodejs/docs/docker.mdx | 18 +++++++++--------- python/docs/api/class-frame.mdx | 4 ++-- python/docs/api/class-framelocator.mdx | 4 ++-- python/docs/api/class-locator.mdx | 4 ++-- python/docs/api/class-page.mdx | 4 ++-- 18 files changed, 51 insertions(+), 51 deletions(-) diff --git a/dotnet/docs/api/class-frame.mdx b/dotnet/docs/api/class-frame.mdx index f1875816c4f..72b1f14dbbc 100644 --- a/dotnet/docs/api/class-frame.mdx +++ b/dotnet/docs/api/class-frame.mdx @@ -466,7 +466,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```csharp await Expect(Page @@ -562,7 +562,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```csharp await page.GetByTestId("directions").ClickAsync(); diff --git a/dotnet/docs/api/class-framelocator.mdx b/dotnet/docs/api/class-framelocator.mdx index e234d847ad9..8aa2b93a708 100644 --- a/dotnet/docs/api/class-framelocator.mdx +++ b/dotnet/docs/api/class-framelocator.mdx @@ -183,7 +183,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```csharp await Expect(Page @@ -279,7 +279,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```csharp await page.GetByTestId("directions").ClickAsync(); diff --git a/dotnet/docs/api/class-locator.mdx b/dotnet/docs/api/class-locator.mdx index 731b0c27c30..9909958f24f 100644 --- a/dotnet/docs/api/class-locator.mdx +++ b/dotnet/docs/api/class-locator.mdx @@ -1125,7 +1125,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```csharp await Expect(Page @@ -1221,7 +1221,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```csharp await page.GetByTestId("directions").ClickAsync(); diff --git a/dotnet/docs/api/class-page.mdx b/dotnet/docs/api/class-page.mdx index 47133aaf4f7..965d1c2ae62 100644 --- a/dotnet/docs/api/class-page.mdx +++ b/dotnet/docs/api/class-page.mdx @@ -912,7 +912,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```csharp await Expect(Page @@ -1008,7 +1008,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```csharp await page.GetByTestId("directions").ClickAsync(); diff --git a/java/docs/api/class-frame.mdx b/java/docs/api/class-frame.mdx index b5c7124df7e..8bbab2bfaa1 100644 --- a/java/docs/api/class-frame.mdx +++ b/java/docs/api/class-frame.mdx @@ -466,7 +466,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```java assertThat(page @@ -562,7 +562,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```java page.getByTestId("directions").click(); diff --git a/java/docs/api/class-framelocator.mdx b/java/docs/api/class-framelocator.mdx index 78eedabc22c..14f775b72a0 100644 --- a/java/docs/api/class-framelocator.mdx +++ b/java/docs/api/class-framelocator.mdx @@ -181,7 +181,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```java assertThat(page @@ -277,7 +277,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```java page.getByTestId("directions").click(); diff --git a/java/docs/api/class-locator.mdx b/java/docs/api/class-locator.mdx index fd9468f9731..6b8471740b8 100644 --- a/java/docs/api/class-locator.mdx +++ b/java/docs/api/class-locator.mdx @@ -1125,7 +1125,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```java assertThat(page @@ -1221,7 +1221,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```java page.getByTestId("directions").click(); diff --git a/java/docs/api/class-page.mdx b/java/docs/api/class-page.mdx index b8ef96d794b..2d0a0e0d333 100644 --- a/java/docs/api/class-page.mdx +++ b/java/docs/api/class-page.mdx @@ -914,7 +914,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```java assertThat(page @@ -1010,7 +1010,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```java page.getByTestId("directions").click(); diff --git a/nodejs/docs/api/class-frame.mdx b/nodejs/docs/api/class-frame.mdx index fb9a04d8105..5a4cfc20c10 100644 --- a/nodejs/docs/api/class-frame.mdx +++ b/nodejs/docs/api/class-frame.mdx @@ -467,7 +467,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```js await expect(page.getByRole('heading', { name: 'Sign up' })).toBeVisible(); @@ -555,7 +555,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```js await page.getByTestId('directions').click(); diff --git a/nodejs/docs/api/class-framelocator.mdx b/nodejs/docs/api/class-framelocator.mdx index 821da2350d6..dd879737020 100644 --- a/nodejs/docs/api/class-framelocator.mdx +++ b/nodejs/docs/api/class-framelocator.mdx @@ -183,7 +183,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```js await expect(page.getByRole('heading', { name: 'Sign up' })).toBeVisible(); @@ -271,7 +271,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```js await page.getByTestId('directions').click(); diff --git a/nodejs/docs/api/class-locator.mdx b/nodejs/docs/api/class-locator.mdx index 384d0b0c51c..f97c96208b8 100644 --- a/nodejs/docs/api/class-locator.mdx +++ b/nodejs/docs/api/class-locator.mdx @@ -1126,7 +1126,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```js await expect(page.getByRole('heading', { name: 'Sign up' })).toBeVisible(); @@ -1214,7 +1214,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```js await page.getByTestId('directions').click(); diff --git a/nodejs/docs/api/class-page.mdx b/nodejs/docs/api/class-page.mdx index 007be540f29..10dd26d1967 100644 --- a/nodejs/docs/api/class-page.mdx +++ b/nodejs/docs/api/class-page.mdx @@ -963,7 +963,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: ```js await expect(page.getByRole('heading', { name: 'Sign up' })).toBeVisible(); @@ -1051,7 +1051,7 @@ Consider the following DOM structure. ``` -You can locate the element by it's test id: +You can locate the element by its test id: ```js await page.getByTestId('directions').click(); diff --git a/nodejs/docs/ci.mdx b/nodejs/docs/ci.mdx index 0a2f24df93d..65817107170 100644 --- a/nodejs/docs/ci.mdx +++ b/nodejs/docs/ci.mdx @@ -101,7 +101,7 @@ jobs: name: 'Playwright Tests' runs-on: ubuntu-latest container: - image: mcr.microsoft.com/playwright:v1.58.1-noble + image: mcr.microsoft.com/playwright:v1.58.2-noble options: --user 1001 steps: - uses: actions/checkout@v5 @@ -335,7 +335,7 @@ trigger: pool: vmImage: ubuntu-latest -container: mcr.microsoft.com/playwright:v1.58.1-noble +container: mcr.microsoft.com/playwright:v1.58.2-noble steps: - task: UseNode@1 @@ -359,7 +359,7 @@ Running Playwright on CircleCI is very similar to running on GitHub Actions. In executors: pw-noble-development: docker: - - image: mcr.microsoft.com/playwright:v1.58.1-noble + - image: mcr.microsoft.com/playwright:v1.58.2-noble ``` Note: When using the docker agent definition, you are specifying the resource class of where playwright runs to the 'medium' tier [here](https://circleci.com/docs/configuration-reference?#docker-execution-environment). The default behavior of Playwright is to set the number of workers to the detected core count (2 in the case of the medium tier). Overriding the number of workers to greater than this number will cause unnecessary timeouts and failures. @@ -382,7 +382,7 @@ Jenkins supports Docker agents for pipelines. Use the [Playwright Docker image]( ```groovy pipeline { - agent { docker { image 'mcr.microsoft.com/playwright:v1.58.1-noble' } } + agent { docker { image 'mcr.microsoft.com/playwright:v1.58.2-noble' } } stages { stage('e2e-tests') { steps { @@ -399,7 +399,7 @@ pipeline { Bitbucket Pipelines can use public [Docker images as build environments](https://confluence.atlassian.com/bitbucket/use-docker-images-as-build-environments-792298897.html). To run Playwright tests on Bitbucket, use our public Docker image ([see Dockerfile](./docker.mdx)). ```yml -image: mcr.microsoft.com/playwright:v1.58.1-noble +image: mcr.microsoft.com/playwright:v1.58.2-noble ``` ### GitLab CI @@ -412,7 +412,7 @@ stages: tests: stage: test - image: mcr.microsoft.com/playwright:v1.58.1-noble + image: mcr.microsoft.com/playwright:v1.58.2-noble script: ... ``` @@ -427,7 +427,7 @@ stages: tests: stage: test - image: mcr.microsoft.com/playwright:v1.58.1-noble + image: mcr.microsoft.com/playwright:v1.58.2-noble parallel: 7 script: - npm ci @@ -442,7 +442,7 @@ stages: tests: stage: test - image: mcr.microsoft.com/playwright:v1.58.1-noble + image: mcr.microsoft.com/playwright:v1.58.2-noble parallel: matrix: - PROJECT: ['chromium', 'webkit'] @@ -458,7 +458,7 @@ To run Playwright tests on Google Cloud Build, use our public Docker image ([see ```yml steps: -- name: mcr.microsoft.com/playwright:v1.58.1-noble +- name: mcr.microsoft.com/playwright:v1.58.2-noble script: ... env: @@ -476,7 +476,7 @@ type: docker steps: - name: test - image: mcr.microsoft.com/playwright:v1.58.1-noble + image: mcr.microsoft.com/playwright:v1.58.2-noble commands: - npx playwright test ``` diff --git a/nodejs/docs/docker.mdx b/nodejs/docs/docker.mdx index 21361d61592..9b509d14924 100644 --- a/nodejs/docs/docker.mdx +++ b/nodejs/docs/docker.mdx @@ -22,7 +22,7 @@ This Docker image is intended to be used for testing and development purposes on ### Pull the image ```bash -docker pull mcr.microsoft.com/playwright:v1.58.1-noble +docker pull mcr.microsoft.com/playwright:v1.58.2-noble ``` ### Run the image @@ -34,7 +34,7 @@ By default, the Docker image will use the `root` user to run the browsers. This On trusted websites, you can avoid creating a separate user and use root for it since you trust the code which will run on the browsers. ```bash -docker run -it --rm --ipc=host mcr.microsoft.com/playwright:v1.58.1-noble /bin/bash +docker run -it --rm --ipc=host mcr.microsoft.com/playwright:v1.58.2-noble /bin/bash ``` #### Crawling and scraping @@ -42,7 +42,7 @@ docker run -it --rm --ipc=host mcr.microsoft.com/playwright:v1.58.1-noble /bin/b On untrusted websites, it's recommended to use a separate user for launching the browsers in combination with the seccomp profile. Inside the container or if you are using the Docker image as a base image you have to use `adduser` for it. ```bash -docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright:v1.58.1-noble /bin/bash +docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright:v1.58.2-noble /bin/bash ``` [`seccomp_profile.json`](https://github.com/microsoft/playwright/blob/main/utils/docker/seccomp_profile.json) is needed to run Chromium with sandbox. This is a [default Docker seccomp profile](https://github.com/docker/engine/blob/d0d99b04cf6e00ed3fc27e81fc3d94e7eda70af3/profiles/seccomp/default.json) with extra user namespace cloning permissions: @@ -82,7 +82,7 @@ You can run Playwright Server in Docker while keeping your tests running on the Start the Playwright Server in Docker: ```bash -docker run -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.58.1-noble /bin/sh -c "npx -y playwright@1.58.1 run-server --port 3000 --host 0.0.0.0" +docker run -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.58.2-noble /bin/sh -c "npx -y playwright@1.58.2 run-server --port 3000 --host 0.0.0.0" ``` #### Connecting to the Server @@ -105,7 +105,7 @@ const browser = await playwright['chromium'].connect('ws://127.0.0.1:3000/'); If you need to access local servers from within the Docker container: ```bash -docker run --add-host=hostmachine:host-gateway -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.58.1-noble /bin/sh -c "npx -y playwright@1.58.1 run-server --port 3000 --host 0.0.0.0" +docker run --add-host=hostmachine:host-gateway -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.58.2-noble /bin/sh -c "npx -y playwright@1.58.2 run-server --port 3000 --host 0.0.0.0" ``` This makes `hostmachine` point to the host's localhost. Your tests should use `hostmachine` instead of `localhost` when accessing local servers. @@ -138,9 +138,9 @@ Once this is enabled you can open the port specified in a new browser tab and yo See [all available image tags]. We currently publish images with the following tags: -- `:v1.58.1` - Playwright v1.58.1 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). -- `:v1.58.1-noble` - Playwright v1.58.1 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). -- `:v1.58.1-jammy` - Playwright v1.58.1 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish). +- `:v1.58.2` - Playwright v1.58.2 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). +- `:v1.58.2-noble` - Playwright v1.58.2 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). +- `:v1.58.2-jammy` - Playwright v1.58.2 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish). :::note @@ -164,7 +164,7 @@ To run Playwright inside Docker, you need to have Node.js, [Playwright browsers] ```Dockerfile FROM node:20-bookworm -RUN npx -y playwright@1.58.1 install --with-deps +RUN npx -y playwright@1.58.2 install --with-deps ``` diff --git a/python/docs/api/class-frame.mdx b/python/docs/api/class-frame.mdx index 158cf2c58d4..46494ac1cc6 100644 --- a/python/docs/api/class-frame.mdx +++ b/python/docs/api/class-frame.mdx @@ -714,7 +714,7 @@ Consider the following DOM structure. ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: Itinéraire ``` -You can locate the element by it's test id: +You can locate the element by its test id: Submit ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: Itinéraire ``` -You can locate the element by it's test id: +You can locate the element by its test id: Submit ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: Itinéraire ``` -You can locate the element by it's test id: +You can locate the element by its test id: Submit ``` -You can locate each element by it's implicit role: +You can locate each element by its implicit role: Itinéraire ``` -You can locate the element by it's test id: +You can locate the element by its test id: