docs: 1.57 release notes #38267
Merged
docs: 1.57 release notes #38267
+127
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ltsuda
reviewed
Nov 18, 2025
| and can help you understand where your test suite is taking longer than expected. | ||
| Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should! | ||
|
|
||
| ### Chrome for Testing |
Contributor
There was a problem hiding this comment.
I'm sorry to bother, but does this change anything related to #33566? / https://playwright.dev/docs/release-notes#try-new-chromium-headless ?
I don't know what I'm actually wanting to ask but does Playwright still provides this "old" Chromium Headless (1.48 figure/ --only-shell) or everything is using the new "new headless" (section "Opt-in to new headless
")?
Please ignore if this question if it doesn't make sense.
Contributor
There was a problem hiding this comment.
Nothing changes in regards to headless shell, new headless and headed.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
dgozman
approved these changes
Nov 20, 2025
| and can help you understand where your test suite is taking longer than expected. | ||
| Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should! | ||
|
|
||
| ### Chrome for Testing |
Contributor
There was a problem hiding this comment.
Nothing changes in regards to headless shell, new headless and headed.
| - [`method: Locator.description`] returns locator description previously set with [`method: Locator.describe`], and `Locator.toString()` now uses the description when available. | ||
| - New option [`option: Locator.click.steps`] in [`method: Locator.click`] and [`method: Locator.dragTo`] that configures the number of `mousemove` events emitted while moving the mouse pointer to the target element. | ||
| - [Service Worker network events](./service-workers.md#network-events-and-routing) are now reported to [BrowserContext](./api/class-browsercontext.md) and its routes. You can opt out using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK` environment variable. | ||
| - New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`]. |
Contributor
There was a problem hiding this comment.
Suggested change
| - New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`]. |
| - New option [`option: Locator.click.steps`] in [`method: Locator.click`] and [`method: Locator.dragTo`] that configures the number of `mousemove` events emitted while moving the mouse pointer to the target element. | ||
| - [Service Worker network events](./service-workers.md#network-events-and-routing) are now reported to [BrowserContext](./api/class-browsercontext.md) and its routes. You can opt out using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK` environment variable. | ||
| - New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`]. | ||
| - Option [`property: TestConfig.webServer`] added a `wait` field to check readiness based on stdout/stderr. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Option [`property: TestConfig.webServer`] added a `wait` field to check readiness based on stdout/stderr. |
| }); | ||
| ``` | ||
|
|
||
| If your webserver runs on varying ports, use `wait` to capture the port: |
Contributor
There was a problem hiding this comment.
This is good, but I think we should expand the webserver guide, link from this doc to the guide, and perhaps trim this doc instead.
Co-authored-by: Dmitry Gozman <[email protected]> Signed-off-by: Simon Knott <[email protected]>
Contributor
Test results for "MCP"2 flaky2430 passed, 116 skipped Merge workflow run. |
Contributor
Test results for "tests 1"5 flaky40316 passed, 787 skipped Merge workflow run. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.