[Webkit-unassigned] [Bug 252664] New: REGRESSION: Previewing projects broken in Construct 3 web app with Safari TP 163

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=252664

            Bug ID: 252664
           Summary: REGRESSION: Previewing projects broken in Construct 3
                    web app with Safari TP 163
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebKit Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ashley at scirra.com

This is a major regression with our web app in Safari TP 163. It prevents users from being able to preview their work.

Steps to reproduce:

1. Open this link in Safari TP 163: https://editor.construct.net/#open=ghost-shooter-tut (dismiss any dialogs or prompts along the way)
2. Press F5, or click the "Play" button on the toolbar, to preview the project (you may need to approve popups)

Expected result: the game should preview in a popup window.

Observed result: the preview window gets stuck saying "Loading". In the console there are 404 errors for missing files. However these are all files served by a Service Worker, and aren't actually on the server. Therefore this indicates an incompatibility with Service Workers in Safari TP 163.

What I suspect is happening here is our engine is now feature-detecting OffscreenCanvas now that Safari TP supports all the necessary features. In our engine this is gated on supporting OffscreenCanvas, module type workers, and the User Activation API. These are all newly supported in Safari TP and so our engine is now creating a module worker to load the engine in ready for rendering off main thread with OffscreenCanvas. However the preview relies on the Service Worker being able to serve some local assets for specific URLs, which are the ones that are returning 404 not found in the console. Therefore I suspect the issue is that module type workers change something about how requests get routed through the SW and this breaks our web app. However I would point out that this has been supported for a long time by Chrome and has been working correctly there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230221/0ec4cab0/attachment.htm>