RESOLVED FIXED Bug 239846
Register shared workers as service worker clients
https://bugs.webkit.org/show_bug.cgi?id=239846
Summary Register shared workers as service worker clients
youenn fablet
Reported 2022-04-28 05:17:08 PDT
Register shared workers as service worker clients
Attachments
Patch (5.78 KB, patch)
2022-04-28 05:21 PDT, youenn fablet
ews-feeder: commit-queue-
Patch (6.13 KB, patch)
2022-04-28 05:48 PDT, youenn fablet
no flags
Patch (6.12 KB, patch)
2022-05-02 07:11 PDT, youenn fablet
no flags
youenn fablet
Comment 1 2022-04-28 05:21:48 PDT
youenn fablet
Comment 2 2022-04-28 05:48:12 PDT
Chris Dumez
Comment 3 2022-04-28 10:56:08 PDT
Comment on attachment 458522 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=458522&action=review > Source/WebCore/workers/shared/context/SharedWorkerThreadProxy.h:52 > + WEBCORE_EXPORT static bool isEmpty(); This function name is super confusing. What does it mean for a SharedWorkerProxy to be empty? I'd suggest something like hasInstances() but I'd be open to suggestions. I don't think we should land "isEmpty()" though.
youenn fablet
Comment 4 2022-04-28 23:34:28 PDT
(In reply to Chris Dumez from comment #3) > Comment on attachment 458522 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=458522&action=review > > > Source/WebCore/workers/shared/context/SharedWorkerThreadProxy.h:52 > > + WEBCORE_EXPORT static bool isEmpty(); > > This function name is super confusing. What does it mean for a > SharedWorkerProxy to be empty? > I'd suggest something like hasInstances() but I'd be open to suggestions. I > don't think we should land "isEmpty()" though. Agreed hasInstances is better
youenn fablet
Comment 5 2022-05-02 07:11:04 PDT
EWS
Comment 6 2022-05-02 09:30:58 PDT
Committed r293665 (250169@main): <https://commits.webkit.org/250169@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 458678 [details].
Radar WebKit Bug Importer
Comment 7 2022-05-02 09:31:16 PDT
Note You need to log in before you can comment on or make changes to this bug.