It would be quite useful to have more context on ServiceWorker related trace events when doing deep dives (i.e. being able to follow a request for a specific assets across SW, CacheStorage, Network, Renderer, etc.)

Use case: being able to explain where/how time is spent for resource request when a service worker is involved regardless of the underlying strategy (i.e. cache first, networkOnly, etc.).

Some examples:
 - URL in Renderer=>SW=>ServiceWorkerContextClient::DispatchFetchEvent
 - URL in Renderer=>SW=>CacheStorageMsg_CacheMatchSuccess
 - URL in Browser=>IOThread=>ServiceWorkerHostMsg_FetchEventResponse
 - URL in Browser=>ServiceWorkerVersion=>ServiceWorkerVersion::Request

There might other places where context would be useful.

UI support to facilitate following the request across process/threads would be nice but just getting enough context should be useful.

Attached a trace as a reference.
 

Deleted: trace_aliexpress.json.gz 3.7 MB

trace_aliexpress.json.gz 3.7 MB Download