Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)

Maybe:
- the push subscriptions could be defined as operating in terms of a service worker scope
- the scope "/" can be treated specially, with it being allowed for there to be a push subscription for scope "/" without there actually being a registration.  And it would be mandated that we would not actually create a registration for "/", so getRegistrations() after a window push subscription would not change anything.
- the push subscription algorithms can use the [scope to job queue map](https://w3c.github.io/ServiceWorker/#dfn-scope-to-job-queue-map) and maybe even the job coalescing system for registering/unregistering in order to provide sequencing sanity.
  - Right now the current hand-waving of "Each [push subscription](https://w3c.github.io/push-api/#dfn-push-subscription) is associated with a [service worker registration](https://www.w3.org/TR/service-workers/#dfn-service-worker-registration)" somewhat side-steps the need to be explicit about this.  But step 7 of [the subscribe method](https://w3c.github.io/push-api/#subscribe-method) "Let registration be [this](https://webidl.spec.whatwg.org/#this)'s associated [service worker registration](https://www.w3.org/TR/service-workers/#dfn-service-worker-registration)." arguably already mandates this.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/368#issuecomment-2318273604
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/pull/368/c2318273604@github.com>