[w3c/push-api] Navigator.push manager (PR #368)

Part of https://github.com/w3c/push-api/issues/360

This PR introduces: 

 * navigator.pushManager
 * makes changes to the various method/algorithms of `pushManager` to distinguish between service worker scope and running in a regular window.

Discussion (or stuff I'm not sure happy with):

* Using the "environment settings object" is probably not the best here, because Workers are also an environment (or have an environment settings object).

The current spec is currently hand-wavy about how push registrations are persistently associated with a service worker (which is ok), but not it gets a little bit messier because we need to distinguish between the Window object associated registration and the service worker ones. 

Anyone got any suggestions as to what I could use to hand the registration off instead?     

 

The following tasks have been completed:

 * [ ] Modified Web platform tests (link to pull request)

Implementation commitment:
 
 * [ ] Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=)
 * [ ] Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)
 * [ ] WebKit (https://bugs.webkit.org/show_bug.cgi?id=)

You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/push-api/pull/368

-- Commit Summary --

  * Introduce 'push subscription owner' concept
  * Expose pushManager on Navigator

-- File Changes --

    M index.html (147)

-- Patch Links --

https://github.com/w3c/push-api/pull/368.patch
https://github.com/w3c/push-api/pull/368.diff

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

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