-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Playwright: update @playwright/test to version 1.52.0 #69932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playwright: update @playwright/test to version 1.52.0 #69932
Conversation
await page | ||
.getByRole( 'document', { name: 'Block: Paragraph' } ) | ||
.first() | ||
.click(); | ||
|
||
// Use Shift+click to select a range. | ||
await page.keyboard.down( 'Shift' ); | ||
await page.keyboard.press( 'ArrowDown' ); | ||
await page.keyboard.press( 'ArrowDown' ); | ||
await page.keyboard.up( 'Shift' ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whenever I try selecting all blocks using primary+a
, the block toolbar briefly appears and then disappears before the next UI update occurs. The current change fixes it.
Interestingly, I haven’t been able to reproduce this behavior in manual testing. I'd appreciate any insights or thoughts on what might be causing this and how to go about fixing the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very strange, I was able to reproduce this issue as well.
e94efec6a98ea17a80a5d2d6a65fbb0e.mp4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found a consistent way to reproduce it, but gave up on tracking down the actual problem 😅. I'm not sure if it's worth it since I don't think it would happen in real-world scenarios.
Steps
- Ensure editor is non-iframed, by installing a block with
apiVersions: 2
. - Add multiple blocks and select them for grouping.
- Change the default grouping block while blocks are selected -
setGroupingBlockName
. - Notice that after clicking on Group action blocks get deselected and nothing happens.
- If you repeat the steps, everything works correctly. So it probably has something to do with already rendered toolbar 🤷
P.S. Everything works correctly with the iframed editor. This is how I fixed the failing e2e test in #70503.
Screencast
CleanShot.2025-07-30.at.14.54.57.mp4
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
@@ -306,7 +306,7 @@ test.describe( 'Multi-block selection (@firefox, @webkit)', () => { | |||
|
|||
await page | |||
.getByRole( 'document', { name: 'Block: Paragraph' } ) | |||
.click( { modifiers: [ 'Shift' ] } ); | |||
.dblclick( { modifiers: [ 'Shift' ] } ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly, the e2e tests here seem to only pass when I use dblclick
🤔.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
I suspect that the fact that two E2E tests failed is due to different versions of Chromium:
- Playwright 1.51: 134.0.6998.35
- Playwright 1.52: 136.0.7103.25
Changing the E2E tests themselves may mask the error, so it may be better to temporarily disable the storybook smoke test until we know the exact cause.
I agree. It appears that both tests requiring change are related to multi-selection. If the feature doesn't work with the latest Chrome version, we need to investigate the issue. |
I've merged #69943, which skips the Storybook smoke test. However, it would be a good idea to leave this PR open to investigate any issues that may arise in the latest browsers. |
@yogeshbhutkar, with your permission, I will close this PR. I'll continue work in #70503 and try to debug the failing tests. |
What?
This PR updates the @playwright/test package to version 1.52.0
What's new?
https://playwright.dev/docs/release-notes#version-152
Breaking Changes (Source: Playwright version 1.52.0 release notes)
Testing Instructions
P.S. This PR also temporarily fixes the failing storybook smoke test (until the next playwright update occurs), which I believe would be caused by mismatching versions of
@playwright/tests
, inclusive of thepeerDependencies
.