Re: [w3c/push-api] Declarative Web Push (Issue #360)

Thanks for answering the other questions, I'm all `👍` with your answers. Also agree for the `"data"`-only use case to not work.

> That would introduce a situation where - in a SW context - you have two ways to get to the PushManager. Which is... not necessarily problematic but... is weird.

From the [Explainer prose](https://github.com/w3c/push-api/issues/360#issuecomment-1768916183:~:text=Push%20subscriptions%20are,in%20the%20other.):

> Push subscriptions are interchang[e]able. An existing push subscription that was made via a ServiceWorkerRegistration whose scope happens to match the security origin of a window object will be visible to that window.navigator.pushManager

> Conversely, a new push subscription made via window.navigator.pushManager will be visible to a ServiceWorkerRegistration whose scope matches that security origin. Removing the subscription from one will be reflected in the other.

There's some interchangeability built into the proposal already, so having two ways of accessing the push manager doesn't seem overly surprising to me at least. 

> The use case isn't as compelling, but it could be?

It's mostly just a question I had. Not sure if there would be user demand. 


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

Message ID: <w3c/push-api/issues/360/1770551964@github.com>