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

>     1. I think the overloading is nice as it allows for reusing an existing subscription. And that ends up working in both directions. And of course you don't have to implement it as a dummy "service worker registration", that would be more of a specification device.

I'm confused by this.  Are you suggesting that if a window registers a push subscription and the origin did not previously have a service worker registration for the scope "/" then a browser would be equally compliant if getRegistrations() returned or did not return a new registration with scope "/"?

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

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