Yury Semikhatsky

There is no clipboard isolation between different tests as of today. https://github.com/microsoft/playwright/issues/8114 is the master bug for tracking clipboard support.

You can probably use [getAnimations](https://developer.mozilla.org/en-US/docs/Web/API/Element/getAnimations) and check if all/some of the animations have finished. Something like this: ```js const dropdown = await page.locator('.dropdown'). closeDropdown() await dropdown.evaluate(e => Promise.all(e.getAnimations({ subtree: true...

We can add a sugar API for this if there is enough interest, leaving this request open to see if there is enough demand.

This is a confirmation dialog for opening external url handler. These dialogs are not currently instrumented in Chromium and not exposed by Playwright in any form. Looking at the Chromium...

> I am running the `Apple M1 chip` with `macOS Big Sur 11.6`. Would I be able to take this issue @yury-s @mxschmitt ? Although I only tried on x86...

Similarly to [test fixture](https://playwright.dev/docs/next/test-fixtures#test-fixtures) you can do it in a separate file and then import `test` from that file to your tests: ```ts // testWithBeforeEach.ts import { test } from...

As the error says you need to rename `hooks_ex.spec.js` to use `.mjs` extension.

You also should not mix require with import, this worked locally: ```js // hooks_ex.spec.mjs import { expect } from '@playwright/test'; import test from './hooks.mjs' test.describe('Security Tests', () => { test('Login...

@Tomsk666 sorry for misleading you, this will not work as I thought, if you run with --workers=1 the hooks will only run in the test file that happens to be...

Another way (more convoluted but also more idiomatic to playwright) to do this is to define your beforeAll/Each methods as [fixtures](https://playwright.dev/docs/next/test-fixtures#worker-fixtures) that run automatically. The documentation covering this is quite...