Chrome for Testing

Starting with this release, Playwright switches from Chromium, to usingChrome 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, pleasefile an issue.

On Arm64 Linux, Playwright continues to use Chromium.

Breaking Change

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

New APIs

• worker.on("console") event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir.worker.expect_event() can be used to wait for it.
• locator.description() returns locator description previously set withlocator.describe().
• New optionsteps inlocator.click() andlocator.drag_to() that configures the number ofmousemove events emitted while moving the mouse pointer to the target element.
• Network requests issued byService Workers are now reported and can be routed through theBrowserContext, only in Chromium. You can opt out using thePLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK environment variable.
• Console messages from Service Workers are dispatched throughworker.on("console"). You can opt out of this using thePLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE environment variable.

Browser Versions

• Chromium 143.0.7499.4
• Mozilla Firefox 144.0.2
• WebKit 26.0