Re: [w3c/manifest] Clarify ServiceWorkerRegistrationObject’s purpose (#800)

> Maybe if we believe that, this is a good place to start: remove `scope` from `ServiceWorkerRegistrationObject`, and always use the manifest scope, so that we enforce the rule that a service worker formally linked to an app manifest has the same scope as that app.

This would mean that we can’t replicate all possible Service Worker configurations in the manifest, which might break the requirement:

> Talked to @marcoscaceres and this appears to be a request in terms of syncing apps that never really materialized.

> This was requested by Microsoft so that apps being installed from the Microsoft Store could install the service worker and populate cache while being installed but without needing the user to access the site.

Also, as there can be more than one service worker script under a manifest scope, shouldn’t `serviceworker` actually take a list of registrations? I’m thinking of large applications (e.g. `https://example.com`) where different teams implement their own service worker for their segment (e.g. `https://example.com/profile/`, `https://example.com/inbox/`, …).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/800#issuecomment-533413504