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

Issue 875013 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 878452

Blocking:
issue 874222



Sign in to add a comment

add PerformanceResourceTiming attributes for measuring cache.match() in a service worker

Project Member Reported by wanderview@chromium.org, Aug 16

Issue description

Sites trying to analyze the performance of a service worker need to understand what is happening between when the FetchEvent is fired and the FetchEvent.respondWith() promise is resolved.  One common activity for service workers is to call `cache.match()` and use the resulting Response to fulfill the `respondWith()` promise.

Let's investigate adding `.cacheMatchStart` and `.cacheMatchEnd` for tracking these values.  This will work as long as the cache-provided Response is passed to `respondWith()` without the service worker re-packing it into a different Response, etc.

This will require updating the spec, WPT, and getting agreement from other browsers.
 
Cc: ralp...@google.com jimmyshen@google.com dsemi@google.com
Blockedon: 878452
Status: WontFix (was: Assigned)
We decided to go with FetchEvent Worker Timing instead.  See bug 900700.

Sign in to add a comment