ServiceWorker with default scope hangs at subscribe call
Reported by
gajduk.a...@gmail.com,
Dec 17 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Expose a service worker at a non-root location with the "Service-Worker-Allowed: /" header 2. Register the service worker from the client side 3. Attempt to subscribe via the pushManager What is the expected behavior? Get a valid subscription or some error What went wrong? The subscription promise just hangs no result or error. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 63.0.3239.84 Channel: n/a OS Version: 10.0 Flash Version: Works on both Opera and Firefox
,
Dec 28 2017
@Reporter: Could you please provide sample URL/test file to check this issue. This would help in further triaging of the issue. Thanks!
,
Jan 2 2018
Figured out I was missing the ready call.
I had
navigator.serviceWorker.register("js/worker.js",{ scope: '/' })
.then(function(registration) { ... });
But I should have used ready to elaying code execution until a service worker is active.
navigator.serviceWorker.register("js/worker.js",{ scope: '/' }).ready
.then(function(registration) { ... });
I don't think this was a bug at all. Sorry to have wasted your time.
,
Jan 2 2018
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 3 2018
As per comment #3, closing the issue as WontFix. Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Dec 18 2017