wanderview / fetchevent-worker-timing Goto Github PK

Instead of adding an interface specific to adding a performance entry related information to FetchEvent as currently proposed, add a FetchEvent as an optional argument to performance.mark.

This would avoid duplicating a very similar logic in two different places and avoids the layering violation of FetchEvent being aware of performance API.

This will allow the passing of meta data and other API benefits currently being proposed as well as future improvements for performance.mark to automatically benefit service workers.

@mattto asked how redirects should be handled. This is a good question.

For cross-origin navigations we should probably clear any FetchEvent Worker Timing entries.

For same-origin or subresource loads its a bit less clear. We could carry the entries over. Or we could clear them.