New issue
Advanced search Search tips

Issue 601924 link

Starred by 5 users
Status: Fixed
Owner:
horo@chromium.org
Closed: Sep 2016
Cc:
pfeldman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature

Blocking:
issue 436917



Sign in to add a comment

Explore automatically logging Service Worker lifecycle events

Project Member Reported by jmadler@google.com, Apr 8 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36

Steps to reproduce the problem:
N/A

What is the expected behavior?

What went wrong?
N/A

Did this work before? N/A 

Chrome version: 49.0.2623.110  Channel: n/a
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0

It can be hard to debug lifecycle events for Service Workers, such as failed SW install.  DevTools could automatically log SW lifecycle events.

Comment 1 by manoranj...@chromium.org, Apr 8 2016

Labels: -Type-Bug Type-Feature
Status: Untriaged (was: Unconfirmed)
This seems to be a new feature request. Hence marking it as 'Untriaged'.

Comment 2 by paulir...@chromium.org, Apr 8 2016

Blocking: 436917
Cc: pfeldman@chromium.org
Components: Blink>ServiceWorker
Owner: horo@chromium.org
Status: Assigned (was: Untriaged)
Yeah I think this is key.  Even with the SW panel, we should have logs to help orient users. 

Appcache actually has some automatic logging for cached resources, so ours will be slightly different. I'm thinking these would work:

Service Worker #1: Registering…
Service Worker #1: Registered.
Service Worker #1: Installing…
Service Worker #1: Installed.
Service Worker #1: Activation starting…
Service Worker #1: Activated…

Service Worker #1: Unregistered.

Comment 3 Deleted

Project Member

Comment 4 by sheriffbot@chromium.org, Jun 3 2016

Labels: Hotlist-Google

Comment 5 by seththompson@chromium.org, Sep 20 2016

Status: Fixed (was: Assigned)
Fixed with Application panel.
►

Sign in to add a comment