Dmitry Gozman

Also need to update #14298 and merge it into docs.

Proposed solution: `npm init playwright@latest --no-browsers`

For the record, running the following in PowerShell before starting Playwright seems to work around the issue: ```powershell #Start-Process -FilePath 'C:\Users\ContainerAdministrator\AppData\Local\ms-playwright\firefox-1352\firefox\firefox.exe' -ArgumentList '--headless --screenshot shot.png about:blank' -Wait ```

I read this as a feature request to somehow change `page.evaluate()` in the html/trace to a custom title, am I right? As a workaround, wrap percy snapshot with a `test.step()`...

@unlikelyzero Red, as any other failed step 😄

@vladyslavlopa I just tried this on M1, and there is no performance difference between chrome and chromium when I `page.goto('https://google.com/')`. Perhaps something's different in your setup? You can try recording...

See also https://github.com/microsoft/playwright/issues/9648#issuecomment-953400441 for more cases where Chromium lacks post data.

See https://github.com/microsoft/playwright/issues/15853 for another repro.

@kevin940726 Thank you for the issue! I can reproduce this. In WebKit and Firefox, this fires `dragover` event, but in Chromium it does not. All browsers fire `dragenter`. Looking at...

I discussed this with the team, and we decided to keep the behavior that's aligned with the browsers. We didn't come up with a good way to mitigate the issue,...