[Bug]: WebKit tests significantly slower when using forms

[DrMueller]

Version

1.49.0

Steps to reproduce

steps:

1. Clone the repository from https://github.com/DrMueller/PlayWrightNetPerformance.
2. Run the Create_Individual test with 50 iterations.
3. Observe the difference in execution time between Chromium and Webkit.

I’ve also experimented with other tests, such as loading weather data from the Blazor example app. However, in these tests, no significant performance discrepancies were observed. It appears that using forms has a notable performance impact on Webkit, but this is just my assumption, as Blazor might also have an impact.

Expected behavior

• Webkit tests using forms have roughly the same performance as with Firefox and Chromium

Actual behavior

• Webkit test being around 2 (sometimes about 5) times slower than Chromium and Firefox

Additional context

The PlayWright repository appears to have similar issues, as noted in this GitHub issue. In my case, videos are not executed anyway (as I'm not configuring a video path), but I’ve added the following code to my tests (see the reproduction repository):

if (browserToTest == BrowserToTest.Webkit)
{
    await context.Tracing.StartAsync(new TracingStartOptions
    {
        Screenshots = true,
        Snapshots = true,
        Sources = true
    });
}

This adjustment improves test stability slightly, but the underlying problem still persists.

Environment

- Operating System: Windows 11 Pro
- CPU: 12th Gen Intel(R) Core(TM) i7-1270P   2.20 GHz
- Browser: [All, Chromium , WebKit]
- .NET Version (TFM): [net9.0]