New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 848332 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Service-Worker delivered events aren't easily serialized/deserialized for debugging

Project Member Reported by slightlyoff@chromium.org, May 31 2018

Issue description

As we have been looking into integration of more events delivered to Service Workers which may not have documents associated with them (e.g., Background Sync, Background Fetch, Notifications, etc.), the current debugging situation continues to be a problem for developers (including large Google teams).

One idea we previously discussed was the ability to export the logged content (and state) of Service Workers and their events ala chrome:net-internals.

There are several options for accomplishing this:

 * extending chrome:net-internals with SW event lifecycle data (perhaps a new tab?) to re-use the existing serialization/deserialization infrastructure
 * extending chrome:serviceworker-internals with this capability

Regardless of which approach we take for internals, devtools will probably want to expose better/more data about these events somehow. Perhaps via some ability to view "historical" events from the SW logs when re-opening devtools on a site?
 

Comment 1 by peter@chromium.org, Jun 1 2018

Cc: -bever...@google.com peter@chromium.org
Status: Available (was: Untriaged)
I can see how something like net-internals for SW events would be useful. It probably would better belong in a SW internals page or DevTools.

Sign in to add a comment