cant update the service-worker after a push was displayed
Reported by
shai...@gmail.com,
May 7 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. create a push notification push registration page and service-worker using https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web 2. trigger a push message, using the developer tools or any other method (push displayed) 3. change something in the service-worker code. 4. navigate to the created push registration page. What is the expected behavior? the service-worker should update What went wrong? the updated service-worker state is "waiting to activate". It only updates itself after a restart of the browser. Did this work before? No Does this work in other browsers? N/A Chrome version: 57.0.2987.133 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0 I've used the skipWaiting() method in the service-worker code, and the registration.update() method when naviating to the push registration page
,
May 15 2017
,
Jun 30 2017
Service Worker team: this seems odd, I've checked both code paths that can invoke the `push` event (real and DevTools) and both properly mark sending the simple event as done. Is there something else keeping it alive?
,
Jul 31 2017
Sorry for the late reply. I recall briefly looking at code paths when asked and couldn't see anything either, so didn't make a comment. It looks like the next step here is to investigate and see if we can reproduce. Could the Blink-Worker triager attempt to do that? Leaving Unconfirmed for that purpose.
,
Aug 3 2017
What happens when you close the devtools and reopen?
,
Jan 5 2018
Closing based on the time since last update. Please feel free to open a new issue if this still persists. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, May 12 2017