[Bug]: Site does not load on webkit browser (build webkit-2083)

[johnboygit]

Version

1.48.0

Steps to reproduce

Unfortunately I'm unable to provide exact steps to reproduce this problem because it only seems to happen against our internal application (React/VueJS). However, I know I'm not the only one experiencing issues as discussed here on Discord... https://discord.com/channels/807756831384403968/1303272702659919902

What I have noticed is that the latest build of webkit (2083) is failing to load our site but if I go back to build 2070 it loads fine. I can also see from testing on LambdaTest that the same build of webkit works fine on MacOS but also fails on Windows.

It's difficult even to get much info from the network logs as it doesn't even seem to get to the first page of the site.

If I can find a public site that demonstrates the behaviour I will update this issue.

Apologies that I can't provide better info at the moment.

Expected behavior

Site should load

Actual behavior

Site does not load

Additional context

Although this is reported against Playwright .NET I don't think it is .NET specific as discussed on Discord

Environment

- Operating System: Windows 10
- Browser: WebKit
- CPU: Intel i7
- .NET Version (TFM): [net8.0]

[johnboygit]

Note that I can reproduce this by simply using the browsers deployed to %userprofile%\appdata\local\ms-playwright without actually needing to run any automated test

[pavelfeldman]

Thanks for the report. Unfortunately, we can't help if we can't reproduce the issue. Please ask those affected to contribute the scenario if they have any.

[fujii]

@johnboygit : Is it producible with the upstream Windows WebKit ? https://docs.webkit.org/Ports/WindowsPort.html#downloading-build-artifacts-from-buildbot
Any errors are reported on the WebInspector console?

[johnboygit]

I used the build here: https://build.webkit.org/#/builders/1192/builds/2178 and it seems to work fine with that one.

[pavelfeldman]

@johnboygit I'll have to close it as non-actionable if there is no scenario we can run. Our builds can deviate from what you download from the builds @ webkit, so it might be that some experimental feature that we enable to match Technical Preview triggers erroneous behavior.

[JanLechvar]

fixed for me in 1.49