⬆️ Updates playwright monorepo to v1.16.2 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
playwright-chromium (source)	^1.14.0 -> 1.16.2
playwright-core (source)	^1.14.0 -> 1.16.2

---

Release Notes

Microsoft/playwright

v1.16.2

Compare Source

Highlights

This patch includes bug fixes for the following issues:

https://github.com/microsoft/playwright/issues/7818 - [Bug]: dedup snapshot CSS imageshttps://github.com/microsoft/playwright/issues/97411 - [BUG] Error while an attempt to install Playwright in CI -> Failed at the playwright@1.16.1 install scriphttps://github.com/microsoft/playwright/issues/975656 - [Regression] Page.screenshot does not work inside Docker with BrowserServhttps://github.com/microsoft/playwright/issues/9759759 - [BUG] 1.16.x the package.json is not export anymhttps://github.com/microsoft/playwright/issues/97609760 - [BUG] snapshot updating causes failures for all tries except the https://github.com/microsoft/playwright/issues/9768/9768 - [BUG] ignoreHTTPSErrors not working on page.request

Browser Versions

• 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

---

(1.16.2-1635322350000)

v1.16.1

Compare Source

Highlights

This patch includes bug fixes for the following issues:

https://github.com/microsoft/playwright/issues/9688 - [REGRESSION]: toHaveCount does not work anymore with 0 elementshttps://github.com/microsoft/playwright/issues/96922 - [BUG] HTML report shows locator._withElement for locator.evaluate

Browser Versions

• 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

---

(1.16.0-1634781227000)

v1.16.0

Compare Source

🎭 Playwright Test

API Testing

Playwright 1.16 introduces new API Testing that lets you send requests to the server directly from Node.js!
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 [page.request][page.request] API:

import { test, expect } from '@​playwright/test';

test('context fetch', async ({ page }) => {
  // Do a GET request on behalf of page
  const response = await page.request.get('http://example.com/foo.json');
  // ... 
});

To do a stand-alone request from node.js to an API endpoint, use new [request fixture][request fixture]:

import { test, expect } from '@​playwright/test';

test('context fetch', async ({ request }) => {
  // Do a GET request on behalf of page
  const response = await request.get('http://example.com/foo.json');
  // ... 
});

Read more about it in our API testing guide.

Response Interception

It is now possible to do response interception by combining API Testing with request interception.

For example, we can blur all the images on the page:

import { test, expect } from '@​playwright/test';
import jimp from 'jimp'; // image processing library

test('response interception', async ({ page }) => {
  await page.route('**/*.jpeg', async route => {
    const response = await page._request.fetch(route.request());
    const image = await jimp.read(await response.body());
    await image.blur(5);
    route.fulfill({
      response,
      body: await image.getBufferAsync('image/jpeg'),
    });
  });
  const response = await page.goto('https://playwright.dev');
  expect(response.status()).toBe(200);
});

Read more about response interception.

New HTML reporter

Try it out new HML reporter with either --reporter=html or a reporter entry
in playwright.config.ts file:

$ npx playwright test --reporter=html

The HTLM reporter has all the information about tests and their failures, including surfacing
trace and image artifacts.

Read more about our reporters.

🎭 Playwright Library

locator.waitFor

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:

import { test, expect } from '@​playwright/test';

test('context fetch', async ({ page }) => {
  const completeness = page.locator('text=Success');
  await completeness.waitFor();
  expect(await page.screenshot()).toMatchSnapshot('screen.png');
});

Read more about [locator.waitFor()][locator.waitFor()].

🎭 Playwright Trace Viewer

• web-first assertions inside trace viewer
• run trace viewer with npx playwright show-trace and drop trace files to the trace viewer PWA
• API testing is integrated with trace viewer
• better visual attribution of action targets

Read more about Trace Viewer.

Browser Versions

• 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

---

(1.16.0-1634781227000)

v1.15.2

Compare Source

Highlights

This patch includes bug fixes for the following issues:

https://github.com/microsoft/playwright/issues/9261 - [BUG] npm init playwright fails on path spaceshttps://github.com/microsoft/playwright/issues/92988 - [Question]: Should new Headers methods work in RouteAsync ?

Browser Versions

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

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

• Google Chrome 93
• Microsoft Edge 93

---

1.15.2-1633455481000

v1.15.1

Compare Source

Highlights

This patch includes bug fixes for the following issues:

#​9065 - [BUG] browser(webkit): disable COOP support
#​9092 - [BUG] browser(webkit): fix text padding
#​9048 - [BUG] fix(test-runner): toHaveURL respect baseURL
#​8955 - [BUG] fix(inspector): stop on all snapshottable actions
#​8921 - [BUG] fix(test runner): after hooks step should not be nested
#​8975 - [BUG] feat(fetch): support form data and json encodings
#​9071 - [BUG] fix(fetch): be compatible with a 0 timeout
#​8999 - [BUG] fix: do not dedup header values
#​9038 - [BUG] fix: restore support for slowmo connect option

Browser Versions

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

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

• Google Chrome 93
• Microsoft Edge 93

---

1.15.0-1633020276000

v1.15.0

Compare Source

🎭 Playwright Library

🖱️ Mouse Wheel

By using Page.mouse.wheel you are now able to scroll vertically or horizontally.

📜 New Headers API

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

• Request.allHeaders()
• Request.headersArray()
• Request.headerValue(name: string)
• Response.allHeaders()
• Response.headersArray()
• Response.headerValue(name: string)
• Response.headerValues(name: string)

🌈 Forced-Colors emulation

Its now possible to emulate the forced-colors CSS media feature by passing it in the context options or calling Page.emulateMedia().

New APIs

• Page.route() accepts new times option to specify how many times this route should be matched.
• Page.setChecked(selector: string, checked: boolean) and Locator.setChecked(selector: string, checked: boolean) was introduced to set the checked state of a checkbox.
• Request.sizes() Returns resource size information for given http request.
• BrowserContext.tracing.startChunk() - Start a new trace chunk.
• BrowserContext.tracing.stopChunk() - Stops a new trace chunk.

🎭 Playwright Test

🤝 test.parallel() run tests in the same file in parallel

test.describe.parallel('group', () => {
  test('runs in parallel 1', async ({ page }) => {
  });
  test('runs in parallel 2', async ({ page }) => {
  });
});

By default, tests in a single file are run in order. If you have many independent tests in a single file, you can now run them in parallel with test.describe.parallel(title, callback).

🛠 Add --debug CLI flag

By using npx playwright test --debug it will enable the Playwright Inspector for you to debug your tests.

Browser Versions

• Chromium 96.0.4641.0
• Mozilla Firefox 92.0
• WebKit 15.0

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

• Google Chrome 93
• Microsoft Edge 93

v1.14.1

Compare Source

Highlights

This patch includes bug fixes for the following issues:

#​8287 - [BUG] webkit crashes intermittently: "file data stream has an unexpected number of bytes"
#​8281 - [BUG] HTML report crashes if diff snapshot does not exists
#​8230 - Using React Selectors with multiple React trees
#​8366 - [BUG] Mark timeout in isVisible as deprecated and noop

Browser Versions

• Chromium 94.0.4595.0
• Mozilla Firefox 91.0
• WebKit 15.0

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

• Google Chrome 92
• Microsoft Edge 92

v1.14.0

Compare Source

🎭 Playwright Library

⚡️ New "strict" mode

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!
await page.click('button', { strict: true });

📍 New Locators API

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!

const locator = page.locator('button');
await locator.click();

Learn more in the documentation.

🧩 Experimental React and Vue selector engines

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.

await page.click('_react=SubmitButton[enabled=true]');
await page.click('_vue=submit-button[enabled=true]');

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

✨ New nth and visible selector engines

• 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
await button.click('button >> nth=0');
// or if you are using locators, you can use first(), nth() and last()
await page.locator('button').first().click();

// click a visible button
await button.click('button >> visible=true');

🎭 Playwright Test

✅ Web-First Assertions

expect now supports lots of new web-first assertions.

Consider the following example:

await expect(page.locator('.status')).toHaveText('Submitted');

Playwright Test 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 either pass this timeout or configure it once via the testProject.expect value in test config.

By default, the timeout for assertions is not set, so it'll wait forever, until the whole test times out.

List of all new assertions:

• expect(locator).toBeChecked()
• expect(locator).toBeDisabled()
• expect(locator).toBeEditable()
• expect(locator).toBeEmpty()
• expect(locator).toBeEnabled()
• expect(locator).toBeFocused()
• expect(locator).toBeHidden()
• expect(locator).toBeVisible()
• expect(locator).toContainText(text, options?)
• expect(locator).toHaveAttribute(name, value)
• expect(locator).toHaveClass(expected)
• expect(locator).toHaveCount(count)
• expect(locator).toHaveCSS(name, value)
• expect(locator).toHaveId(id)
• expect(locator).toHaveJSProperty(name, value)
• expect(locator).toHaveText(expected, options)
• expect(page).toHaveTitle(title)
• expect(page).toHaveURL(url)
• expect(locator).toHaveValue(value)

⛓ Serial mode with describe.serial

Declares a group of tests that should always be run serially. If one of the tests fails, all subsequent tests are skipped. All tests in a group are retried together.

test.describe.serial('group', () => {
  test('runs first', async ({ page }) => { /* ... */ });
  test('runs second', async ({ page }) => { /* ... */ });
});

Learn more in the documentation.

🐾 Steps API with test.step

Split long tests into multiple steps using test.step() API:

import { test, expect } from '@​playwright/test';

test('test', async ({ page }) => {
  await test.step('Log in', async () => {
    // ...
  });
  await test.step('news feed', async () => {
    // ...
  });
});

Step information is exposed in reporters API.

🌎 Launch web server before running tests

To launch a server during the tests, use the webServer option in the configuration file. The server will wait for a given port to be available before running the tests, and the port will be passed over to Playwright as a baseURL when creating a context.

// playwright.config.ts
import { PlaywrightTestConfig } from '@​playwright/test';
const config: PlaywrightTestConfig = {
  webServer: {
    command: 'npm run start', // command to launch
    port: 3000, // port to await for 
    timeout: 120 * 1000, 
    reuseExistingServer: !process.env.CI,
  },
};
export default config;

Learn more in the documentation.

Browser Versions

• Chromium 94.0.4595.0
• Mozilla Firefox 91.0
• WebKit 15.0

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

• Google Chrome 92
• Microsoft Edge 92

v1.13.1

Compare Source

Highlights

This patch includes bug fixes for the following issues:

#​7800 - [Bug]: empty screen when opening trace.zip
#​7785 - [Bug]: Channel installation requires curl/wget on the system
#​7746 - [Bug]: global use is not working to launch firefox or webkit
#​7849 - [Bug]: Setting the current shard through config uses n+1 instead

Browser Versions

• Chromium 93.0.4576.0
• Mozilla Firefox 90.0
• WebKit 14.2

v1.13.0

Compare Source

Playwright Test

• ⚡️ Introducing Reporter API which is already used to create an Allure Playwright reporter.
• ⛺️ New baseURL fixture to support relative paths in tests.

Playwright

• 🖖 Programmatic drag-and-drop support via the [page.dragAndDrop()][page.dragAndDrop()] API.
• 🔎 Enhanced HAR with body sizes for requests and responses. Use via recordHar option in [browser.newContext()][browser.newContext()].

Tools

• Playwright Trace Viewer now shows parameters, returned values and console.log() calls.
• Playwright Inspector can generate Playwright Test tests.

New and Overhauled Guides

• Intro
• Authentication
• Chome Extensions
• Playwright Test Configuration
• Playwright Test Annotations
• Playwright Test Fixtures

Browser Versions

• Chromium 93.0.4576.0
• Mozilla Firefox 90.0
• WebKit 14.2

New Playwright APIs

• new baseURL option in [browser.newContext()][browser.newContext()] and [browser.newPage()][browser.newPage()]
• [response.securityDetails()][response.securityDetails()] and [response.serverAddr()][response.serverAddr()]
• [page.dragAndDrop()][page.dragAndDrop()] and [frame.dragAndDrop()][frame.dragAndDrop()]
• [download.cancel()][download.cancel()]
• [page.inputValue()][page.inputValue()], [frame.inputValue()][frame.inputValue()] and [elementHandle.inputValue()][elementHandle.inputValue()]
• new force option in [page.fill()][page.fill()], [frame.fill()][frame.fill()], and [elementHandle.fill()][elementHandle.fill()]
• new force option in [page.selectOption()][page.selectOption()], [frame.selectOption()][frame.selectOption()], and [elementHandle.selectOption()][elementHandle.selectOption()]

v1.12.3

Compare Source

Highlights

This patch release includes bug fixes for the following issues:

#​7085 - [BUG] Traceviewer screens are not recorded well when using constructable stylesheets
#​7093 - Folder for a test-case is getting generated in test-results even if Test Case Passes when properties are given on Failure
#​7099 - [test-runner] Missing types for the expect library
#​7124 - [Test Runner] config.outputDir must be an absolute path
#​7141 - [Feature] Options for video resolution
#​7163 - [Test runner] artifacts are removed
#​7223 - [BUG] test-runner viewport can't be null
#​7284 - [BUG] incorrect @​playwright/test typings for toMatchSnapshot/toMatchInlineSnapshot/etc
#​7304 - [BUG] Snapshots are not captured if there is an animation at the beginning
#​7326 - [BUG] When PW timeouts, last trace action does not get collected[BUG] When PW timeouts, last trace action does not get collected

Browser Versions

• 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

v1.12.2

Compare Source

Highlights

This patch release includes bugfixes for the following issues:

• #​7015 - [BUG] Firefox: strange undefined toJSON property on JS objects
• #​7004 - [test runner] Error: Error while reading global-setup.ts: Cannot find module 'global-setup.ts'
• #​7048 - [BUG] Dialogs cannot be dismissed if tracing is on in Chromium or Webkit
• #​7058 - [BUG] Getting no video frame error for mobile chrome
• #​7020 - [Feature] Codegen should be able to emit @​playwright/test syntax

Browser Versions

• 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

v1.12.1

Compare Source

Highlights

This patch includes bug fixes for the following issues:

#​6984 - slowMo does not exist in type 'Fixtures<{}, {}, PlaywrightTestOptions, PlaywrightWorkerOptions>'
#​6982 - [trace viewer] srcset sanitization removes space between values, hence breaks the links
#​6981 - [BUG] Getting "Please install @​playwright/test package to use Playwright Test."

Browser Versions

• 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

v1.12.0

Compare Source

⚡️ Introducing Playwright Test

Playwright Test is a new test runner built from scratch by Playwright team specifically to accommodate end-to-end testing needs:

• Run tests across all browsers.
• Execute tests in parallel.
• Enjoy context isolation and sensible defaults out of the box.
• Capture traces, videos, screenshots and other artifacts on failure.
• Infinitely extensible with fixtures.

Installation:

npm i -D @​playwright/test

Simple test tests/foo.spec.ts:

import { test, expect } from '@​playwright/test';

test('basic test', async ({ page }) => {
  await page.goto('https://playwright.dev/');
  const name = await page.innerText('.navbar__title');
  expect(name).toBe('Playwright');
});

Running:

npx playwright test

👉 Read more in testrunner documentation.

🧟‍♂️ Introducing Playwright Trace & TraceViewer

Playwright TraceViewer 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
• browse network during script execution

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

const browser = await chromium.launch();
const context = await browser.newContext();

// Start tracing before creating / navigating a page.
await context.tracing.start({ screenshots: true, snapshots: true });

const page = await context.newPage();
await page.goto('https://playwright.dev');

// Stop tracing and export it into a zip archive.
await context.tracing.stop({ path: 'trace.zip' });

Traces are examined later with the Playwright CLI:

npx playwright show-trace trace.zip

That will open the following GUI:

👉 Read more in trace viewer documentation.

---

Browser Versions

• 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

New APIs

• reducedMotion option in [page.emulateMedia()][page.emulateMedia()], [browserType.launchPersistentContext()][browserType.launchPersistentContext()], [browser.newContext()][browser.newContext()] and [browser.newPage()][browser.newPage()]
• [browserContext.on('request')][browserContext.on('request')]
• [browserContext.on('requestfailed')][browserContext.on('requestfailed')]
• [browserContext.on('requestfinished')][browserContext.on('requestfinished')]
• [browserContext.on('response')][browserContext.on('response')]
• tracesDir option in [browserType.launch()][browserType.launch()] and [browserType.launchPersistentContext()][browserType.launchPersistentContext()]
• new [browserContext.tracing][browserContext.tracing] API namespace
• new [download.page()][download.page()] method
• new options in [electron.launch()][electron.launch()]:
  • acceptDownloads
  • bypassCSP
  • colorScheme
  • extraHTTPHeaders
  • geolocation
  • httpCredentials

Issues Closed (41)

#​1094 - [Feature] drag and drop
#​3320 - [Feature] Emulate reduced motion media query
#​4054 - [REGRESSION]: chromium.connect does not work with vanilla CDP servers anymore
#​5189 - [Bug] Codegen generates goto for page click
#​4535 - [Feature] page.waitForResponse support for async predicate function
#​4704 - [BUG] Unable to upload big file on firefox.
#​4752 - [Feature] export the screenshot options type
#​5136 - [BUG] Yarn install (yarn 2) does not install chromium from time to time.
#​5151 - [Question] Playwright + Firefox: How to disable download prompt and allows it to save by default?
#​5446 - [BUG] Use up to date Chromium version in device User-Agents
#​5501 - [BUG] Can't run Playwright in Nix
#​5510 - [Feature] Improve documentation, document returned type for all methods
#​5537 - [BUG] webkit reports incorrect download url
#​5542 - [BUG] HTML response is null on requestfinished when opening popup
#​5617 - [BUG] [Codegen] Page click recorded as click + goto
#​5695 - [BUG] Uploading executable file in firefox browser
#​5753 - [Question] - Page.click fails
#​5775 - [Question] Firefox Error: NS_BINDING_ABORTED [Question]
#​5947 - [Question] about downloads with launchPersistentContext
#​5962 - [BUG?] Download promises don't resolve when using Chromium instead of Firefox in headful mode
#​6026 - [BUG] Node.js 16 results in DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field with file import
#​6137 - Chromium Issue while loading a page
#​6239 - [BUG] Blank screenshot saved after test failure in CI
#​6240 - [Question] Can't wait for an element to be visible when it is overlapped with other elements in frontend
#​6264 - [BUG?] Mouse actions produce different result depending on slowMo setting
#​6340 - [Feature] Capture network requests on BrowserContext
#​6373 - Stream or capture Video into buffer [Question]
#​6390 - [devops] workaround Chromium windows issues with swiftshader
#​6403 - [BUG] Chromium - Playwright not intercepting importScripts requests in WebWorker
#​6415 - [BUG] Browsers will not start in GitLab pipeline
#​6431 - [BUG] Device emulation not working with CLI
#​6439 - [BUG] screencast tests fail on Mac10.14
#​6447 - [Question] How to use map function in $
#​6453 - [BUG] Firefox / Webkit: Unable to click element in iframe (Frame has been detached)
#​6460 - getDisplayMedia in headless
#​6469 - [BUG] Screencast & video metabug
#​6473 - [Feature] allow custom args for ffmpeg in VideoRecorder.ts
#​6477 - [BUG] webkit can disable mouse when evaluating specified JavaScript code
#​6480 - [Feature] on('selector' ...
#​6483 - [Question] How to set path for local exe?
#​6485 - [BUG] Cannot download a file in /tmp/ with a Snap browser

Commits (342)

d22fa86 - devops: update trigger for firefox beta builder
12d8c54 - chore: swap firefox-stable and firefox (#​6950)
bd193ca - feat: nicer stub for WebKit on MacOS 10.14 (#​6948)
55da16d - Revert "feat: switch to the Firefox Stable equivalent by default (#​6926)" (#​6947)
a1e8d2d - feat: switch to the Firefox Stable equivalent by default (#​6926)
15668f0 - chore: make WebKit @​ MacOS 10.14 error more prominent (#​6943)
d0eaec3 - chore: clarify that we download Playwright browser builds (#​6938)
334096e - docs(pom): fixed JS example which contained TS (#​6917)
52878bb - docs: use proper option name for --workers (#​6942)
99ec32a - chore: more doc nits (#​6937)
8960584 - fix(chromium): drag and drop works in chromium (#​6207)
42a9e4a - docs(mobile): make experimental Android support more present (#​6932)
8c13f67 - fix(test runner): remove folio/jest namespaces in expect matchers (#​6930)
cfd49b5 - feat: support npx playwright install msedge (#​6861)
46a0213 - chore: remove internal uses of "folio" (#​6931)
b556ee6 - chore: brush up playwright-test types (#​6928)
f745bf1 - chore: bring in folio source (#​6923)
d4e50be - fix: do not install media pack on non-server windows (#​6925)
4b5ad33 - doc: fix first .net script (#​6922)
82041b2 - test: roll to folio@0.4.0-alpha28 (#​6918)
f441755 - docs(dotnet): add test runner docs (#​6919)
69b7346 - fix: various test-related fixes (#​6916)
a836466 - fix(tracing): error handling (#​6888)
b5ac393 - docs(showcase): fixed typo in showcase.md (#​6915)
9ad507d - doc(test): pass through test docs (#​6914)
ec2b6a7 - test: add a glob test (#​6911)
ff3ad7a - fix(android): to not call Browser.setDownloadBehavior (#​6913)
9142d8c - docs: fix that test-runner is not included (#​6912)
233f187 - feat(inspector): remove snapshots (#​6909)
a96491c - feat(downloads): subscribe to download events in Browser domain instead of Page (#​6082)
e37c078 - test(nonStallingRawEvaluateInExistingMainContext): fix broken test (#​6908)
21b00d0 - test: roll to folio@0.4.0-alpha27 (#​6897)
85786b1 - feat(trace viewer): fix UI issues (#​6890)
cfcf6a8 - feat: use WebKit stub on MacOS 10.14 (#​6892)
657aa04 - browser(webkit): import to fix win compilation (#​6895)
abc66c6 - docs(api): add missing callback parameter to waitForRequestFinished (#​6893)
2663c0b - browser(webkit): import to fix mac compilation (#​6894)
cce62da - browser(webkit): roll to 06/03 (#​6889)
fb0004c - feat(webkit): bump to 1492 (#​6887)
8a81b11 - devops: replace WebKit for MacOS 10.14 build with a stub (#​6886)
401dcfd - chore: do not use a subshell hack when using XVFB (#​6884)
f264e85 - chore: bump dependency to fix vulnerability (#​6882)
d4482f3 - chore: do not use Array.from in injected script (#​6876)
f2cc439 - chore: move electron back from FYI bots to CQ1 bots (#​6883)
b19b2dc - devops: introduce manual @​next NPM publishing (#​6881)
e41979a - chore: import @​playwright/test (#​6880)
375ceca - test: disable chromium headed tracing test (#​6878)
0830c85 - test: roll to folio@0.4.0-alpha26 (#​6877)
d7c202c - browser(webkit): fix time formatting and mac compilation (#​6875)
064150f - chore: use fs.promises API instead of promisify (#​6871)
d16afef - doc(tracing): add a trace viewer doc (#​6864)
3de3a88 - feat(test): introduce npx playwright test (#​6816)
13b6444 - docs(python): add docs for installing with conda (#​6845)
cc2c691 - test: roll to folio@0.4.0-alpha25 (#​6863)
b2143a9 - chore: make tracing zero config (#​6859)
837ee08 - fix(waitForSelector): retry when context is gone during node adoption (#​6851)
8a68fa1 - docs(test runner): advanced section (#​6862)
c09726b - test: add tests for port-forwarding via playwrightclient (#​6860)q
4fa792e - browser(webkit): getLocalStorageData command (#​6858)
c5e1c8b - docs: use explicit tab suffixes (#​6855)
e91e49e - feat(port-forwarding): add playwrightclient support (#​6786)
33c2f6c - chore: do not bundle api.json and protocol.yml (#​6841)
254ec15 - feat(user-agent): Adding User-Agent in headers while making connection to browser (#​6813)
17b6f06 - feat: install media pack on windows with npx playwright install-deps (#​6836)
2fde9bc - fix(webkit): use new awaitPromise parameter instead of separate command (#​6852)
d28f45b - api(tracing): export -> stop({path}) (#​6802)
79b244a - chore: use bash instead of sh in code blocks (#​6847)
f9c8b78 - feat(webkit): bump to 1490 (#​6842)
ec7d37d - chore: update eslint config (#​6840)
831a1c8 - feat(firefox-stable): roll Firefox-Stable to Firefox v89 (#​6833)
ffe89c4 - docs(installation): use RFC5735 IPs for examples (#​6729)
919d258 - feat: support npx playwright install chrome (#​6835)
1020d3d - feat(webkit): bump to 1488 (#​6826)
251c7d8 - test: properly disable electron test (#​6839)
d767fc2 - browser(firefox-stable): disable proton UI in firefox stable (#​6838)
a1106e5 - test: disable test that fails on Electron (#​6837)
c9613b3 - devops: introduce "FYI" test bots (#​6834)
cb4adb1 - feat: install chrome-beta via cli (#​6831)
3c3a7f9 - feat(chromium): roll Chromium to r888113 (#​6832)
4f5b65f - chore: update package-lock.json to v2 (#​6830)
24dca96 - chore: remove electron/android from build_packages (#​6827)
b4ffe86 - browser(webkit): add missing override annotations (#​6829)
9b81dcc - browser(webkit): add awaitPromise parameter to Runtime.callFunctionOn (#​6828)
d79110d - fix(port-forwarding): close socket on unexpected payloads (#​6753)
531d35f - browser(chromium): revert swiftshader fixes (#​6824)
17585a3 - devops: do not run tests for docs cha

---

Configuration

📅 Schedule: "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow.

🚦 Automerge: Disabled due to failing status checks.

♻ Rebasing: Whenever PR is behind base branch, 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, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[changelogg]

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

[renovate]

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/alexrogalskiy/styled-screenshots/4V5xPYeaTFZDn3FC815dhunouwNQ
✅ Preview: https://styled-screenshots-git-renovate-playwright-c8bf5c-alexrogalskiy.vercel.app

[vercel]

Deployment failed with the following error:

Resource is limited - try again after in 30 minutes (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again after in 28 minutes (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again after in 2 hours (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again after in 46 minutes (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again after in 47 minutes (more than 100, code: "api-deployments-free-per-day").

[mergify]

This pull request has merge conflicts that must be resolved before it can be merged. @renovate[bot] please rebase it. https://rook.io/docs/rook/master/development-flow.html#updating-your-fork