- From: Yoshisato Yanagisawa <notifications@github.com>
- Date: Wed, 04 Jun 2025 18:30:27 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 5 June 2025 01:30:31 UTC
yoshisatoyanagisawa left a comment (w3c/ServiceWorker#1642) I have been thinking about the implementation aspects of this proposal. The proposed lifecycle for the `ServiceWorkerRegistration` here is a significant departure from the current model. This leads me to believe we would need to build a new registration and unregistration flow from the ground up. Is that a correct understanding? Then, we would likely also need a new, distinct API to avoid any confusion with the standard Service Worker APIs. The specification itself would require a major effort to clearly delineate the two concepts. Considering the high potential costs for both implementation and specification work, I am wondering about the use cases that would motivate vendors to undertake this. I am concerned that without a strong cost-benefit argument, adoption among vendors could be challenging. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1642#issuecomment-2942406559 You are receiving this because you are subscribed to this thread. Message ID: <w3c/ServiceWorker/issues/1642/2942406559@github.com>
Received on Thursday, 5 June 2025 01:30:31 UTC