The WebKit version used by Playwright is not exactly Safari — it's a custom build, and not all features (like media or touch events) behave identically to Safari on macOS, testing WebKit on Windows doesn't fully replace testing on Safari/macOS if you're aiming for real-world parity.

If your 3D model site relies heavily on WebGL, canvas, or GPU-accelerated rendering, and especially if Safari support is important, then:

• Test Chromium on Windows.

• Test WebKit on Windows for basic parity.

• Test WebKit on macOS for accurate Safari-like behavior (optional but ideal).

• Use real Safari (manual or CI via macOS runners) for full coverage, especially for production-critical paths.

A 3D scene might render slightly differently on macOS Safari (WebKit) due to its WebGL backend, even if the same test passes on Windows WebKit (Playwright uses a patched version of WebKit, not Safari itself).

Hugs!